Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31aa7769938e8f3e415683a6e3e969eb38f10c1dcc16ecfdf939a958e6ac204d

Tx prefix hash: 024159a352a97b1b1c4891930b4e9eb27bd91f176685e7a36e94d2fc4e9b5dd4
Tx public key: cae264be2ce93df462ec05c8367a1ed60314935015dfde563aae3bed5c41f296
Timestamp: 1703000653 Timestamp [UCT]: 2023-12-19 15:44:13 Age [y:d:h:m:s]: 01:322:23:55:34
Block: 916626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489670 RingCT/type: yes/0
Extra: 01cae264be2ce93df462ec05c8367a1ed60314935015dfde563aae3bed5c41f296021100000003e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f721c320b4e36e784e4a9e490bf81ca1890ba79b6cbbf0ea3623549715ce4d 0.600000000000 1374184 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": 916636, "vin": [ { "gen": { "height": 916626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f721c320b4e36e784e4a9e490bf81ca1890ba79b6cbbf0ea3623549715ce4d" } } ], "extra": [ 1, 202, 226, 100, 190, 44, 233, 61, 244, 98, 236, 5, 200, 54, 122, 30, 214, 3, 20, 147, 80, 21, 223, 222, 86, 58, 174, 59, 237, 92, 65, 242, 150, 2, 17, 0, 0, 0, 3, 228, 187, 107, 131, 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