Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 176717800dfcb0c69fa2e0d59c91f4a1c9851535af826eb720396bd9e25bc2b7

Tx prefix hash: 28a15faf14a2c431a25b5adede13cb73a4f8fffefacad59242e6fb1d0dfa86db
Tx public key: ad651ded84b5510bfe2fd91fc033d4e954cfba089cd995a865b63c54a36b771f
Timestamp: 1728538014 Timestamp [UCT]: 2024-10-10 05:26:54 Age [y:d:h:m:s]: 00:210:00:17:28
Block: 1128340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149901 RingCT/type: yes/0
Extra: 01ad651ded84b5510bfe2fd91fc033d4e954cfba089cd995a865b63c54a36b771f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67ae1457fd68ceaa7ff05df7e3ebd6e18bce3f0b1fb5eff9a1bf784c41628b0e 0.600000000000 1611157 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": 1128350, "vin": [ { "gen": { "height": 1128340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67ae1457fd68ceaa7ff05df7e3ebd6e18bce3f0b1fb5eff9a1bf784c41628b0e" } } ], "extra": [ 1, 173, 101, 29, 237, 132, 181, 81, 11, 254, 47, 217, 31, 192, 51, 212, 233, 84, 207, 186, 8, 156, 217, 149, 168, 101, 182, 60, 84, 163, 107, 119, 31, 2, 17, 0, 0, 0, 5, 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