Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ab7da7042602a40ef88dd72d4a8d4402cba0449d1f429985742616193d77c38

Tx prefix hash: 1dee10f4c190e1efee2ae41a33b66d4fc20194172f301f39444380d5507e6a36
Tx public key: b1ce9d80b16d7c448bb620d89fbc9db2c937d32991a7110e62e6a47262ab8f90
Timestamp: 1706104210 Timestamp [UCT]: 2024-01-24 13:50:10 Age [y:d:h:m:s]: 00:357:10:01:21
Block: 942328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255894 RingCT/type: yes/0
Extra: 01b1ce9d80b16d7c448bb620d89fbc9db2c937d32991a7110e62e6a47262ab8f900211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfa5fc1d0e0f39b289061a296f9a002713cd148c37d9163d28cedcf4c56aeb56 0.600000000000 1400498 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": 942338, "vin": [ { "gen": { "height": 942328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfa5fc1d0e0f39b289061a296f9a002713cd148c37d9163d28cedcf4c56aeb56" } } ], "extra": [ 1, 177, 206, 157, 128, 177, 109, 124, 68, 139, 182, 32, 216, 159, 188, 157, 178, 201, 55, 211, 41, 145, 167, 17, 14, 98, 230, 164, 114, 98, 171, 143, 144, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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