Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f5f85600e6c419a31b26a480b3eadba142cb0d68d3dff291b4de54870de250

Tx prefix hash: ccbedd59ee29c49e2f7246875c2099691506bbc87997ad08a04015b855833608
Tx public key: cf703c781f66ae07eb8c9c9e2de62af8f47e8dcc7a88a4c1839bbbe05f54d07c
Timestamp: 1578193498 Timestamp [UCT]: 2020-01-05 03:04:58 Age [y:d:h:m:s]: 05:301:05:36:51
Block: 38930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1362884 RingCT/type: yes/0
Extra: 01cf703c781f66ae07eb8c9c9e2de62af8f47e8dcc7a88a4c1839bbbe05f54d07c02110000000bd81c26c0000000000000000000

1 output(s) for total of 456.046995194000 dcy

stealth address amount amount idx
00: 45b5e25c4b016ed963bd9416d16544e8d8320e1b4220a8e23eae21d7fcb0a093 456.046995194000 66743 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": 38940, "vin": [ { "gen": { "height": 38930 } } ], "vout": [ { "amount": 456046995194, "target": { "key": "45b5e25c4b016ed963bd9416d16544e8d8320e1b4220a8e23eae21d7fcb0a093" } } ], "extra": [ 1, 207, 112, 60, 120, 31, 102, 174, 7, 235, 140, 156, 158, 45, 230, 42, 248, 244, 126, 141, 204, 122, 136, 164, 193, 131, 155, 187, 224, 95, 84, 208, 124, 2, 17, 0, 0, 0, 11, 216, 28, 38, 192, 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