Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09af4878664cdc92f67ad1e2378567df9bcbfdc3686ca9f15f58f07295577131

Tx prefix hash: 596b58d09e85765780781a75d474cf1a288e26fdc229151d9ae0534a3feb812e
Tx public key: 44ec966cfee977719ca4c0d849f8f7e16b967ae7ceb1ea9f32ae7b565a23ed8a
Timestamp: 1661403873 Timestamp [UCT]: 2022-08-25 05:04:33 Age [y:d:h:m:s]: 02:272:18:08:01
Block: 573286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716217 RingCT/type: yes/0
Extra: 0144ec966cfee977719ca4c0d849f8f7e16b967ae7ceb1ea9f32ae7b565a23ed8a02110000000275e3f0e9000000000000000000

1 output(s) for total of 7.735094036000 dcy

stealth address amount amount idx
00: 7d6b3fa840ecc0ae26c7bd1c891641c896a88a615b91a1dd5acbce40e2412e08 7.735094036000 1006564 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": 573296, "vin": [ { "gen": { "height": 573286 } } ], "vout": [ { "amount": 7735094036, "target": { "key": "7d6b3fa840ecc0ae26c7bd1c891641c896a88a615b91a1dd5acbce40e2412e08" } } ], "extra": [ 1, 68, 236, 150, 108, 254, 233, 119, 113, 156, 164, 192, 216, 73, 248, 247, 225, 107, 150, 122, 231, 206, 177, 234, 159, 50, 174, 123, 86, 90, 35, 237, 138, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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