Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df0245c54c26b23a8195f9854e132ed2bb1ae3023644c9714fc611b106e0374

Tx prefix hash: 41f071ba3069ff9d0d85b62472bf6e5aeee59dc0584c794ee976ff838a5f8024
Tx public key: abba01d34bd25131604f4aa3def90d031eeb61e92f316d733509d4fecf1157ce
Timestamp: 1635666151 Timestamp [UCT]: 2021-10-31 07:42:31 Age [y:d:h:m:s]: 03:099:15:17:22
Block: 364185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849489 RingCT/type: yes/0
Extra: 01abba01d34bd25131604f4aa3def90d031eeb61e92f316d733509d4fecf1157ce02110000000df56b629f000000000000000000

1 output(s) for total of 38.133293618000 dcy

stealth address amount amount idx
00: 573fb5f5976751cacc32f6c7d8b7f93404ebc574e369a81b1238f7c90ab23b0d 38.133293618000 739901 of 0

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": 364195, "vin": [ { "gen": { "height": 364185 } } ], "vout": [ { "amount": 38133293618, "target": { "key": "573fb5f5976751cacc32f6c7d8b7f93404ebc574e369a81b1238f7c90ab23b0d" } } ], "extra": [ 1, 171, 186, 1, 211, 75, 210, 81, 49, 96, 79, 74, 163, 222, 249, 13, 3, 30, 235, 97, 233, 47, 49, 109, 115, 53, 9, 212, 254, 207, 17, 87, 206, 2, 17, 0, 0, 0, 13, 245, 107, 98, 159, 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