Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2fb86e5ba62b99f0004ae3b6dd984b7b311fbc8907c683a36c96c977c5782dd

Tx prefix hash: bb3141888bac900dac78ab85d0877282c07cf638fa1da1881da6a9372236c1f4
Tx public key: c0e867a847f8803710b820d4dae8a240dad07bdcdf25bf2211ba6c006103c123
Timestamp: 1609234686 Timestamp [UCT]: 2020-12-29 09:38:06 Age [y:d:h:m:s]: 03:325:01:00:25
Block: 171314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 985026 RingCT/type: yes/0
Extra: 01c0e867a847f8803710b820d4dae8a240dad07bdcdf25bf2211ba6c006103c1230211000001e3c6b81c9d000000000000000000

1 output(s) for total of 166.098712488000 dcy

stealth address amount amount idx
00: 3d686da6c87ae9bb5358b16705bd46a08f93183d53b14a68a158a8a2e9f611c8 166.098712488000 322449 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": 171324, "vin": [ { "gen": { "height": 171314 } } ], "vout": [ { "amount": 166098712488, "target": { "key": "3d686da6c87ae9bb5358b16705bd46a08f93183d53b14a68a158a8a2e9f611c8" } } ], "extra": [ 1, 192, 232, 103, 168, 71, 248, 128, 55, 16, 184, 32, 212, 218, 232, 162, 64, 218, 208, 123, 220, 223, 37, 191, 34, 17, 186, 108, 0, 97, 3, 193, 35, 2, 17, 0, 0, 1, 227, 198, 184, 28, 157, 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