Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25d8e6badbe61fbb482c7403608d454186217135171d41930ee881e43a4d5de2

Tx prefix hash: 497815a866b5050457c8f8f3d8eae546646e6edac52642948fd9e9c3d66d0426
Tx public key: 4d83f24cd3234ce57c134a760f9b203fab7c6eef9232ce026b8a8b6d0c9e60ff
Timestamp: 1578630762 Timestamp [UCT]: 2020-01-10 04:32:42 Age [y:d:h:m:s]: 04:354:10:33:55
Block: 42204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142874 RingCT/type: yes/0
Extra: 014d83f24cd3234ce57c134a760f9b203fab7c6eef9232ce026b8a8b6d0c9e60ff02110000000f4ac5aa02000000000000000000

1 output(s) for total of 444.796614161000 dcy

stealth address amount amount idx
00: 68188fdc50821e9d925a3f7a53bb62bf9f5367b1ceca7578c47ae59514f159f5 444.796614161000 75940 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": 42214, "vin": [ { "gen": { "height": 42204 } } ], "vout": [ { "amount": 444796614161, "target": { "key": "68188fdc50821e9d925a3f7a53bb62bf9f5367b1ceca7578c47ae59514f159f5" } } ], "extra": [ 1, 77, 131, 242, 76, 211, 35, 76, 229, 124, 19, 74, 118, 15, 155, 32, 63, 171, 124, 110, 239, 146, 50, 206, 2, 107, 138, 139, 109, 12, 158, 96, 255, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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