Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7e7632e3d4b1101a2c462b9a05e1e90b72ef4420bd9ba0d8d420dbe81df28f

Tx prefix hash: 49a1a24bff286c3f9b49969f7de27f87254d4e467b2c9612d7682efcc73d8e5c
Tx public key: 23ef9f4ee34b9121db3d380e37ea73296de80a04f51399bc3d6ca5121572b321
Timestamp: 1730574496 Timestamp [UCT]: 2024-11-02 19:08:16 Age [y:d:h:m:s]: 00:154:06:54:50
Block: 1145137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110106 RingCT/type: yes/0
Extra: 0123ef9f4ee34b9121db3d380e37ea73296de80a04f51399bc3d6ca5121572b3210211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3824cb3657f5443e11d6112193a6d6bbbec09e5a66016291e463b5c13c894310 0.600000000000 1629532 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": 1145147, "vin": [ { "gen": { "height": 1145137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3824cb3657f5443e11d6112193a6d6bbbec09e5a66016291e463b5c13c894310" } } ], "extra": [ 1, 35, 239, 159, 78, 227, 75, 145, 33, 219, 61, 56, 14, 55, 234, 115, 41, 109, 232, 10, 4, 245, 19, 153, 188, 61, 108, 165, 18, 21, 114, 179, 33, 2, 17, 0, 0, 0, 2, 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