Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11e89c1dc2999e2556b45988b1bcbc81df2a60d651f118fbe6e4539336ca8a29

Tx prefix hash: 356d95b2703d726ebdb0a270cdb26df7c79da3b885834d4289e5919fcdfa3c38
Tx public key: 6dc4eea098d5b04a0a874d535635377f53b0c14f601706d37f3ab2cd0c8098aa
Timestamp: 1582341593 Timestamp [UCT]: 2020-02-22 03:19:53 Age [y:d:h:m:s]: 05:255:07:36:33
Block: 70040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1333271 RingCT/type: yes/0
Extra: 016dc4eea098d5b04a0a874d535635377f53b0c14f601706d37f3ab2cd0c8098aa021100000001c71d3ff9000000000000000000

1 output(s) for total of 359.690699662000 dcy

stealth address amount amount idx
00: a55953425b024a8f349290c0cd3bc8fe122e1d8bed9ad23d48e2d25b76289494 359.690699662000 129234 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": 70050, "vin": [ { "gen": { "height": 70040 } } ], "vout": [ { "amount": 359690699662, "target": { "key": "a55953425b024a8f349290c0cd3bc8fe122e1d8bed9ad23d48e2d25b76289494" } } ], "extra": [ 1, 109, 196, 238, 160, 152, 213, 176, 74, 10, 135, 77, 83, 86, 53, 55, 127, 83, 176, 193, 79, 96, 23, 6, 211, 127, 58, 178, 205, 12, 128, 152, 170, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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