Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee901156c24de7b33310ccd8ce234441e40f1701169e30674f2be4386b04934c

Tx prefix hash: 75b5f6cd9add5f6bb1b045cd349df2202f2acc7afde2cc6c2135fb5e96642cda
Tx public key: a69a926f23313d4710cec90e5bdcd2eeb545dc33b93ddea4e9e210c1869e89f2
Timestamp: 1710667042 Timestamp [UCT]: 2024-03-17 09:17:22 Age [y:d:h:m:s]: 01:027:02:24:01
Block: 980200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280337 RingCT/type: yes/0
Extra: 01a69a926f23313d4710cec90e5bdcd2eeb545dc33b93ddea4e9e210c1869e89f20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 277032eeac760cfbc50482076b492c78e89f24e6b58f82e801a550718d86f279 0.600000000000 1440259 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": 980210, "vin": [ { "gen": { "height": 980200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "277032eeac760cfbc50482076b492c78e89f24e6b58f82e801a550718d86f279" } } ], "extra": [ 1, 166, 154, 146, 111, 35, 49, 61, 71, 16, 206, 201, 14, 91, 220, 210, 238, 181, 69, 220, 51, 185, 61, 222, 164, 233, 226, 16, 193, 134, 158, 137, 242, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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