Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ceb71bd86259ebe42167656ee4b77ed6ab4396f118da3051357f71b9a7171cb

Tx prefix hash: 054b1ab479821121865910a0fe90e10bb794e4a74678d442a49e778c0435da22
Tx public key: b62be517ab6a0625bef0bcba0893c8ad122423f3f20de2e7e2ba03f0a0d7be6b
Timestamp: 1736906625 Timestamp [UCT]: 2025-01-15 02:03:45 Age [y:d:h:m:s]: 00:153:20:49:26
Block: 1197565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109679 RingCT/type: yes/0
Extra: 01b62be517ab6a0625bef0bcba0893c8ad122423f3f20de2e7e2ba03f0a0d7be6b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00fd5471b0f623c23b9f066e8f599927fc261003ae5fa5fb0b719258b36ae4d2 0.600000000000 1684178 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": 1197575, "vin": [ { "gen": { "height": 1197565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00fd5471b0f623c23b9f066e8f599927fc261003ae5fa5fb0b719258b36ae4d2" } } ], "extra": [ 1, 182, 43, 229, 23, 171, 106, 6, 37, 190, 240, 188, 186, 8, 147, 200, 173, 18, 36, 35, 243, 242, 13, 226, 231, 226, 186, 3, 240, 160, 215, 190, 107, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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