Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc0ea205d5aa8fb455caccc4daf5453001db794ed47d377f80b8f62ac81f9b33

Tx prefix hash: aee03bb53d9e7f1a8feef7bb627600a74aa61c7100aaceaaa002cbcc525c148e
Tx public key: e4b43b6f7d5a6c9bdd0b985c56021c82f0d74d50aee3fd2a1bb4caeb026802d2
Timestamp: 1699375188 Timestamp [UCT]: 2023-11-07 16:39:48 Age [y:d:h:m:s]: 01:139:13:44:11
Block: 886569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360922 RingCT/type: yes/0
Extra: 01e4b43b6f7d5a6c9bdd0b985c56021c82f0d74d50aee3fd2a1bb4caeb026802d202110000000633af99f4000000000000000000

1 output(s) for total of 0.708645239000 dcy

stealth address amount amount idx
00: 988a2afba0e0590dc82a697d55ea97c5b933ff0d9db45c44f9ae604ea9dd36ad 0.708645239000 1342396 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": 886579, "vin": [ { "gen": { "height": 886569 } } ], "vout": [ { "amount": 708645239, "target": { "key": "988a2afba0e0590dc82a697d55ea97c5b933ff0d9db45c44f9ae604ea9dd36ad" } } ], "extra": [ 1, 228, 180, 59, 111, 125, 90, 108, 155, 221, 11, 152, 92, 86, 2, 28, 130, 240, 215, 77, 80, 174, 227, 253, 42, 27, 180, 202, 235, 2, 104, 2, 210, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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