Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c4344d9134a3fb67492125343a953356ec4fb02214cd56ef3a2ec6b1ce5774

Tx prefix hash: 505adb1c00b392f368c4c94098057e465a3f39fd58e4b8da3a36d80174385a2a
Tx public key: d4ecc96b112e5f5268de5daedae6bbb477f3744cde82a7909a0434e3572c4008
Timestamp: 1733011804 Timestamp [UCT]: 2024-12-01 00:10:04 Age [y:d:h:m:s]: 00:109:06:30:15
Block: 1165328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77911 RingCT/type: yes/0
Extra: 01d4ecc96b112e5f5268de5daedae6bbb477f3744cde82a7909a0434e3572c40080211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38218e46d34895d9169e23001c5f9e2b3d6de70d10a3c3732f11e5784048af4a 0.600000000000 1651003 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": 1165338, "vin": [ { "gen": { "height": 1165328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38218e46d34895d9169e23001c5f9e2b3d6de70d10a3c3732f11e5784048af4a" } } ], "extra": [ 1, 212, 236, 201, 107, 17, 46, 95, 82, 104, 222, 93, 174, 218, 230, 187, 180, 119, 243, 116, 76, 222, 130, 167, 144, 154, 4, 52, 227, 87, 44, 64, 8, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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