Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c53a219e862cc4a02671b3681bad44bc81822e745aeb53e7b1f8f03bcfdd9c5

Tx prefix hash: 5be30ae58f06b03724d361adfc952328d52fc6d6cdeee04e3048c45344aeb7e5
Tx public key: 6f2ff48e2c66ceec176fff6f8e025efec805af45d9213ab9b345480ae24d7d80
Timestamp: 1717414859 Timestamp [UCT]: 2024-06-03 11:40:59 Age [y:d:h:m:s]: 00:288:23:22:54
Block: 1036132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206530 RingCT/type: yes/0
Extra: 016f2ff48e2c66ceec176fff6f8e025efec805af45d9213ab9b345480ae24d7d800211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf9bda5a6e7acfcf6a3e16dfd3a4217cac95fac57dd91f51c637c7611aff506 0.600000000000 1504657 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": 1036142, "vin": [ { "gen": { "height": 1036132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf9bda5a6e7acfcf6a3e16dfd3a4217cac95fac57dd91f51c637c7611aff506" } } ], "extra": [ 1, 111, 47, 244, 142, 44, 102, 206, 236, 23, 111, 255, 111, 142, 2, 94, 254, 200, 5, 175, 69, 217, 33, 58, 185, 179, 69, 72, 10, 226, 77, 125, 128, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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