Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2aa6889a54fd74e508fefd858a93816acd691b33c9e3e237558dd5270babeb5

Tx prefix hash: acad8a8a80f410950eeda4aba323438dcf1f164686ab34052b5c5b6727ff1f55
Tx public key: 3512869f5ceb4ed745d0e905aef16de033c1a0e7a764b6cd23a49187571636e1
Timestamp: 1728242352 Timestamp [UCT]: 2024-10-06 19:19:12 Age [y:d:h:m:s]: 00:204:12:38:42
Block: 1125891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145994 RingCT/type: yes/0
Extra: 013512869f5ceb4ed745d0e905aef16de033c1a0e7a764b6cd23a49187571636e102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36a50b9b0ae31b3cec5e08c2fd860c2e3fedc9e6918c8e66a4b25de45725f6ed 0.600000000000 1608664 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": 1125901, "vin": [ { "gen": { "height": 1125891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36a50b9b0ae31b3cec5e08c2fd860c2e3fedc9e6918c8e66a4b25de45725f6ed" } } ], "extra": [ 1, 53, 18, 134, 159, 92, 235, 78, 215, 69, 208, 233, 5, 174, 241, 109, 224, 51, 193, 160, 231, 167, 100, 182, 205, 35, 164, 145, 135, 87, 22, 54, 225, 2, 17, 0, 0, 0, 3, 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