Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac0b69a20b60ff45a323e398f39fb0066ac3bbacec1274d3f1b65ef2091a2a88

Tx prefix hash: 090607942594d522fc8a6e30fe1e9db623ed30fb4bbd86ef4a072882af5ff2d2
Tx public key: 32de91ad81ff2ad5d5254a19b9519185e67d83143260419ede4ef5ab97822f4c
Timestamp: 1694293538 Timestamp [UCT]: 2023-09-09 21:05:38 Age [y:d:h:m:s]: 01:170:21:52:46
Block: 844622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383220 RingCT/type: yes/0
Extra: 0132de91ad81ff2ad5d5254a19b9519185e67d83143260419ede4ef5ab97822f4c02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.975925710000 dcy

stealth address amount amount idx
00: 4d0ca2320c92824e4d7474968e76dc8993340cb76c76f1e0a8cff8c0d1969b91 0.975925710000 1297942 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": 844632, "vin": [ { "gen": { "height": 844622 } } ], "vout": [ { "amount": 975925710, "target": { "key": "4d0ca2320c92824e4d7474968e76dc8993340cb76c76f1e0a8cff8c0d1969b91" } } ], "extra": [ 1, 50, 222, 145, 173, 129, 255, 42, 213, 213, 37, 74, 25, 185, 81, 145, 133, 230, 125, 131, 20, 50, 96, 65, 158, 222, 78, 245, 171, 151, 130, 47, 76, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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