Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b4a1031a1da5afd37facf2e18970bfc1eb720cb8f58171bc2a926c6bebfd6e

Tx prefix hash: f1b766d7965bec5d716ac1c3d37d84dad317cb5f484c818d126048a29c4608fc
Tx public key: 48dc79d7864a5f3a624c8b42ba2c460efdd86ca45739fcd433abdc69c857af94
Timestamp: 1740988587 Timestamp [UCT]: 2025-03-03 07:56:27 Age [y:d:h:m:s]: 00:256:02:18:08
Block: 1231105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180775 RingCT/type: yes/0
Extra: 0148dc79d7864a5f3a624c8b42ba2c460efdd86ca45739fcd433abdc69c857af940211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac7f9dd3de201d6216b6e0f60e53bd7a201754b0bfbf7cba0a3cfcf4b95b727f 0.600000000000 1718010 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": 1231115, "vin": [ { "gen": { "height": 1231105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac7f9dd3de201d6216b6e0f60e53bd7a201754b0bfbf7cba0a3cfcf4b95b727f" } } ], "extra": [ 1, 72, 220, 121, 215, 134, 74, 95, 58, 98, 76, 139, 66, 186, 44, 70, 14, 253, 216, 108, 164, 87, 57, 252, 212, 51, 171, 220, 105, 200, 87, 175, 148, 2, 17, 0, 0, 0, 16, 31, 10, 83, 235, 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