Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51e6ccc41c2ac104ca97b50e766b7964fc76d6c738b909b43b424c2750475ff7

Tx prefix hash: 1f1ca5ef829f25e40ca40890056b616b8d4bcf152428e504b991c26ce93ab358
Tx public key: b2f7b2a613af35b5099226c460f54a912fa2f28321630d2e284c217581f8aa04
Timestamp: 1710470251 Timestamp [UCT]: 2024-03-15 02:37:31 Age [y:d:h:m:s]: 00:345:04:16:10
Block: 978569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246750 RingCT/type: yes/0
Extra: 01b2f7b2a613af35b5099226c460f54a912fa2f28321630d2e284c217581f8aa040211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c5fe2fa4a64517aa3b1832a33bd9c620213057221139d56f40442a6887bdca5 0.600000000000 1438596 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": 978579, "vin": [ { "gen": { "height": 978569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c5fe2fa4a64517aa3b1832a33bd9c620213057221139d56f40442a6887bdca5" } } ], "extra": [ 1, 178, 247, 178, 166, 19, 175, 53, 181, 9, 146, 38, 196, 96, 245, 74, 145, 47, 162, 242, 131, 33, 99, 13, 46, 40, 76, 33, 117, 129, 248, 170, 4, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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