Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 919336e5c862d0dd78a5f72ff7929377c47b655d50cf0d8812e0dc56513f7e59

Tx prefix hash: 00bcb4f7b70472ba27df1e14070783a00a5871698768b84fb511cdf9ad960abf
Tx public key: 6c9912c3a7e800d253aea5fbf034812550265dd6c8f6eb32b88f2773273089a6
Timestamp: 1725695817 Timestamp [UCT]: 2024-09-07 07:56:57 Age [y:d:h:m:s]: 00:067:05:41:19
Block: 1104779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48078 RingCT/type: yes/0
Extra: 016c9912c3a7e800d253aea5fbf034812550265dd6c8f6eb32b88f2773273089a6021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c713fc2f414943779f3ee3ae32c50de9f3f0ecab16369b161acad08cbe8e905b 0.600000000000 1582054 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1104789, "vin": [ { "gen": { "height": 1104779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c713fc2f414943779f3ee3ae32c50de9f3f0ecab16369b161acad08cbe8e905b" } } ], "extra": [ 1, 108, 153, 18, 195, 167, 232, 0, 210, 83, 174, 165, 251, 240, 52, 129, 37, 80, 38, 93, 214, 200, 246, 235, 50, 184, 143, 39, 115, 39, 48, 137, 166, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8