Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38523f13f7f294c036370f5dd16d470170a7f0183cc392f45142a9a8f9eb0e40

Tx prefix hash: d35ec3124a58c34119e8f0427ef5459ef3582a2c987fdf3b63fb01bc8b18e4f5
Tx public key: f77004deab4c1008e3bb193efdb48c4623d2097ef0408adf3d00d6c965e5bbe2
Timestamp: 1694639646 Timestamp [UCT]: 2023-09-13 21:14:06 Age [y:d:h:m:s]: 01:197:23:34:40
Block: 847490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402598 RingCT/type: yes/0
Extra: 01f77004deab4c1008e3bb193efdb48c4623d2097ef0408adf3d00d6c965e5bbe20211000000024b8f5122000000000000000000

1 output(s) for total of 0.954803232000 dcy

stealth address amount amount idx
00: 33dae9c64badff564454c2e1dbef9b66dbad03a89384af3fea7dd414c8b924c2 0.954803232000 1301016 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": 847500, "vin": [ { "gen": { "height": 847490 } } ], "vout": [ { "amount": 954803232, "target": { "key": "33dae9c64badff564454c2e1dbef9b66dbad03a89384af3fea7dd414c8b924c2" } } ], "extra": [ 1, 247, 112, 4, 222, 171, 76, 16, 8, 227, 187, 25, 62, 253, 180, 140, 70, 35, 210, 9, 126, 240, 64, 138, 223, 61, 0, 214, 201, 101, 229, 187, 226, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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