Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a53d77e17ba411af11f1646cd79093cc4a8fb301572ed671417365fe2d7256

Tx prefix hash: e81f0e46d069a6469587b7c7992a007e562b8b82a4e2ccf7519bd4045547563b
Tx public key: 4bc2b854dac96bf3878af560d96872356fdc6c6a3a2a462a9521650ec1bcd0fa
Timestamp: 1577829404 Timestamp [UCT]: 2019-12-31 21:56:44 Age [y:d:h:m:s]: 05:002:09:16:03
Block: 36026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151685 RingCT/type: yes/0
Extra: 014bc2b854dac96bf3878af560d96872356fdc6c6a3a2a462a9521650ec1bcd0fa02110000004bac34bf9e000000000000000000

1 output(s) for total of 466.263866070000 dcy

stealth address amount amount idx
00: 904ea3311690f4e03f7c04d4af477bb8317b878908a01b1b3f8178839193f034 466.263866070000 60874 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": 36036, "vin": [ { "gen": { "height": 36026 } } ], "vout": [ { "amount": 466263866070, "target": { "key": "904ea3311690f4e03f7c04d4af477bb8317b878908a01b1b3f8178839193f034" } } ], "extra": [ 1, 75, 194, 184, 84, 218, 201, 107, 243, 135, 138, 245, 96, 217, 104, 114, 53, 111, 220, 108, 106, 58, 42, 70, 42, 149, 33, 101, 14, 193, 188, 208, 250, 2, 17, 0, 0, 0, 75, 172, 52, 191, 158, 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