Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 901097a33b5c9cb6054ce920b8e160ebcb284d86cc6aec9d43a7c1b4217706b2

Tx prefix hash: ca9237baf8897ba099c94f4cf2d089e90acb8d842ed7519f9b79366f762fa2ce
Tx public key: 4ea5572afcf5f8ce613a9e96275f1c00483c4cb3f08faa6c8a8f00e36495a953
Timestamp: 1641043570 Timestamp [UCT]: 2022-01-01 13:26:10 Age [y:d:h:m:s]: 02:321:10:37:52
Block: 408178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 747847 RingCT/type: yes/0
Extra: 014ea5572afcf5f8ce613a9e96275f1c00483c4cb3f08faa6c8a8f00e36495a953021100000002e2bb00ee000000000000000000

1 output(s) for total of 27.263201251000 dcy

stealth address amount amount idx
00: 179e182a57d3f73d19a8725a893789e001d0a3d881ec1261478f6e6f576f7432 27.263201251000 810079 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": 408188, "vin": [ { "gen": { "height": 408178 } } ], "vout": [ { "amount": 27263201251, "target": { "key": "179e182a57d3f73d19a8725a893789e001d0a3d881ec1261478f6e6f576f7432" } } ], "extra": [ 1, 78, 165, 87, 42, 252, 245, 248, 206, 97, 58, 158, 150, 39, 95, 28, 0, 72, 60, 76, 179, 240, 143, 170, 108, 138, 143, 0, 227, 100, 149, 169, 83, 2, 17, 0, 0, 0, 2, 226, 187, 0, 238, 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