Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c059200a129a2377f2b6e8c0de13af78836707c75dadb271e6d5550a54c4852d

Tx prefix hash: 1eda301a67dd0469ad4a46c8b47e77d654de95e4fd401c507b44e2236e8b0b8d
Tx public key: 9cae3b045fa2b46399836085a07e615cf8280125b78aed6d4acc8c10b81ad6ef
Timestamp: 1710107721 Timestamp [UCT]: 2024-03-10 21:55:21 Age [y:d:h:m:s]: 01:057:17:28:51
Block: 975549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302275 RingCT/type: yes/0
Extra: 019cae3b045fa2b46399836085a07e615cf8280125b78aed6d4acc8c10b81ad6ef02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b9c7ad30d939ba47eb71f209ed110dce838f76eb02dafa25a208dfd0b10c906 0.600000000000 1435522 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": 975559, "vin": [ { "gen": { "height": 975549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b9c7ad30d939ba47eb71f209ed110dce838f76eb02dafa25a208dfd0b10c906" } } ], "extra": [ 1, 156, 174, 59, 4, 95, 162, 180, 99, 153, 131, 96, 133, 160, 126, 97, 92, 248, 40, 1, 37, 183, 138, 237, 109, 74, 204, 140, 16, 184, 26, 214, 239, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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