Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 807208a73ab13ac19e919759a04dfa12c7436a80760fa5f982fcfa06bc833dbf

Tx prefix hash: 3c8091f42c18a06ba2e3ab2e968f78fe4e688be6ec0538d8133c4555444187cc
Tx public key: bc6a4070d79f6e8a25450570bc627a67905cb933f15d99a10987060bb94b5dde
Timestamp: 1714026897 Timestamp [UCT]: 2024-04-25 06:34:57 Age [y:d:h:m:s]: 00:246:08:17:22
Block: 1008028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176336 RingCT/type: yes/0
Extra: 01bc6a4070d79f6e8a25450570bc627a67905cb933f15d99a10987060bb94b5dde0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c7aaba77ca7c0e4d39748c1dfb06d3fd2a82a4d8e6bc6469b74f09552120f61 0.600000000000 1469494 of 15

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": 1008038, "vin": [ { "gen": { "height": 1008028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c7aaba77ca7c0e4d39748c1dfb06d3fd2a82a4d8e6bc6469b74f09552120f61" } } ], "extra": [ 1, 188, 106, 64, 112, 215, 159, 110, 138, 37, 69, 5, 112, 188, 98, 122, 103, 144, 92, 185, 51, 241, 93, 153, 161, 9, 135, 6, 11, 185, 75, 93, 222, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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