Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcc1cbbc3e2282ea280fc1c162d6567a753e1928af321d1890336deffcda63de

Tx prefix hash: 3a50347814e1e4959c8ebab4133d93b0d7ac70b2c50492fa0bdce76f76140281
Tx public key: 0eeaf9ae20e1619e1d605e2077e8045c831edd7d3fab08c6e5427910a977e10c
Timestamp: 1737164379 Timestamp [UCT]: 2025-01-18 01:39:39 Age [y:d:h:m:s]: 00:339:01:00:18
Block: 1199704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239874 RingCT/type: yes/0
Extra: 010eeaf9ae20e1619e1d605e2077e8045c831edd7d3fab08c6e5427910a977e10c02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 689904d2a53e776a9b3ece0264b00c9a656c24bff6f6a194c6fc13beca3bb87d 0.600000000000 1686337 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": 1199714, "vin": [ { "gen": { "height": 1199704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "689904d2a53e776a9b3ece0264b00c9a656c24bff6f6a194c6fc13beca3bb87d" } } ], "extra": [ 1, 14, 234, 249, 174, 32, 225, 97, 158, 29, 96, 94, 32, 119, 232, 4, 92, 131, 30, 221, 125, 63, 171, 8, 198, 229, 66, 121, 16, 169, 119, 225, 12, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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