Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03a04f7d16afbc7f3d323752ea8dd5c273e9c1accfa8437aeb57c59c3afca05

Tx prefix hash: 67af8c9f2d4aff0cfe996da2fecea7f1557cf8e40e6211a006dd74ece6958dc0
Tx public key: 416ef9fef9049cf762eda2333f09706e7e8d6f1e23636ef1a255a77bbe84f212
Timestamp: 1696869510 Timestamp [UCT]: 2023-10-09 16:38:30 Age [y:d:h:m:s]: 01:085:02:38:38
Block: 866004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322065 RingCT/type: yes/0
Extra: 01416ef9fef9049cf762eda2333f09706e7e8d6f1e23636ef1a255a77bbe84f21202110000000475e3f0e9000000000000000000

1 output(s) for total of 0.829028166000 dcy

stealth address amount amount idx
00: 1150a1070d2ce1950918555effb42a1656bce9e6f3c6882977ba4fe011b8767e 0.829028166000 1320570 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": 866014, "vin": [ { "gen": { "height": 866004 } } ], "vout": [ { "amount": 829028166, "target": { "key": "1150a1070d2ce1950918555effb42a1656bce9e6f3c6882977ba4fe011b8767e" } } ], "extra": [ 1, 65, 110, 249, 254, 249, 4, 156, 247, 98, 237, 162, 51, 63, 9, 112, 110, 126, 141, 111, 30, 35, 99, 110, 241, 162, 85, 167, 123, 190, 132, 242, 18, 2, 17, 0, 0, 0, 4, 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