Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bab42171d67db760f9a0179df2e6cd0a38c7f4a945dcec2497852414ca3ff0b

Tx prefix hash: 0ce8ed04345abf7e1d4273525693cfcee8a8b3853e323b2c5dac92620daf1d64
Tx public key: b8fc4865aa03a3a2ba839149b4a2b558ce5ddc1109faddd1b725a2ef7a673514
Timestamp: 1728438087 Timestamp [UCT]: 2024-10-09 01:41:27 Age [y:d:h:m:s]: 00:243:20:25:50
Block: 1127508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174123 RingCT/type: yes/0
Extra: 01b8fc4865aa03a3a2ba839149b4a2b558ce5ddc1109faddd1b725a2ef7a67351402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b1557e56ba4f71a5c4191f57e48192788142c179e6468ab1ae5029dd87ebcd1 0.600000000000 1610315 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": 1127518, "vin": [ { "gen": { "height": 1127508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b1557e56ba4f71a5c4191f57e48192788142c179e6468ab1ae5029dd87ebcd1" } } ], "extra": [ 1, 184, 252, 72, 101, 170, 3, 163, 162, 186, 131, 145, 73, 180, 162, 181, 88, 206, 93, 220, 17, 9, 250, 221, 209, 183, 37, 162, 239, 122, 103, 53, 20, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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