Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64ce48f2e5d456312411963eb12d97a569ec94d79e8fc76ea9eca9460642b1f

Tx prefix hash: 73732398cec19498954b2a31ecd86af3fda690e44babfeab2d1785d89175d71a
Tx public key: 9ef65f49d3e854599cde8404aef4a87d9f3caafa478e56bb7a4c2ce576ae5d2f
Timestamp: 1716221679 Timestamp [UCT]: 2024-05-20 16:14:39 Age [y:d:h:m:s]: 00:316:23:06:50
Block: 1026235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226546 RingCT/type: yes/0
Extra: 019ef65f49d3e854599cde8404aef4a87d9f3caafa478e56bb7a4c2ce576ae5d2f02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f067793b1e40698e4520ccb09acb7bcff8663df8f2d3ade1d6377b021bbd4ba 0.600000000000 1493206 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": 1026245, "vin": [ { "gen": { "height": 1026235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f067793b1e40698e4520ccb09acb7bcff8663df8f2d3ade1d6377b021bbd4ba" } } ], "extra": [ 1, 158, 246, 95, 73, 211, 232, 84, 89, 156, 222, 132, 4, 174, 244, 168, 125, 159, 60, 170, 250, 71, 142, 86, 187, 122, 76, 44, 229, 118, 174, 93, 47, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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