Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5482dfac7bc7de10bf6cbb6a2ab4d7e3c0cf3347fd94a91eca67c2af50a34f3

Tx prefix hash: 7013e0748f6af716f8912974b1aa33664c7d17313257ce3ab03f25c1c1c4efb5
Tx public key: d0e9891463e6e08baa596b449030356f57e165e2ddd0f99ed87d0fb03e675e07
Timestamp: 1731903316 Timestamp [UCT]: 2024-11-18 04:15:16 Age [y:d:h:m:s]: 01:041:13:17:40
Block: 1156142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288171 RingCT/type: yes/0
Extra: 01d0e9891463e6e08baa596b449030356f57e165e2ddd0f99ed87d0fb03e675e07021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 212828e40d0f819be576fed35195f51b6d1831e3b6bf1cf621510d36efc4abf6 0.600000000000 1641765 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": 1156152, "vin": [ { "gen": { "height": 1156142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "212828e40d0f819be576fed35195f51b6d1831e3b6bf1cf621510d36efc4abf6" } } ], "extra": [ 1, 208, 233, 137, 20, 99, 230, 224, 139, 170, 89, 107, 68, 144, 48, 53, 111, 87, 225, 101, 226, 221, 208, 249, 158, 216, 125, 15, 176, 62, 103, 94, 7, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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