Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf92b2174cadb4d58df4bf1de543c0a2f4246f3b3f3d41a4fb39511b0e49e672

Tx prefix hash: b2a298e4e80d9ac445f7b2a33299ef723be46ab9edffdf3491f96cf2d80fcd1f
Tx public key: 25faa7e80343e5cb5d515e38ae1e5276a3d689ed6afe031129dd15bfabe923c5
Timestamp: 1603301023 Timestamp [UCT]: 2020-10-21 17:23:43 Age [y:d:h:m:s]: 04:039:11:00:32
Block: 142719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1021307 RingCT/type: yes/0
Extra: 0125faa7e80343e5cb5d515e38ae1e5276a3d689ed6afe031129dd15bfabe923c502110000001290939edc000000000000000000

1 output(s) for total of 206.591956649000 dcy

stealth address amount amount idx
00: 6e1a6e1c588b52446011f8cbd0bd0388cd7c77f9b67ee1a9ab04619d8187fa33 206.591956649000 237013 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": 142729, "vin": [ { "gen": { "height": 142719 } } ], "vout": [ { "amount": 206591956649, "target": { "key": "6e1a6e1c588b52446011f8cbd0bd0388cd7c77f9b67ee1a9ab04619d8187fa33" } } ], "extra": [ 1, 37, 250, 167, 232, 3, 67, 229, 203, 93, 81, 94, 56, 174, 30, 82, 118, 163, 214, 137, 237, 106, 254, 3, 17, 41, 221, 21, 191, 171, 233, 35, 197, 2, 17, 0, 0, 0, 18, 144, 147, 158, 220, 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