Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4333b033612a1f04c20698b759a4eb99eb9fdfbd6631ce534ff213cb80cf4e70

Tx prefix hash: 050c87f01cab9ef1a959322e7cb5865ba21ca23f0e29b989f061aa96972549e2
Tx public key: 357819f46d5fc3efdc9c3ed7de1a9ba01d7a49032a1809863643974eef1a7a83
Timestamp: 1745133834 Timestamp [UCT]: 2025-04-20 07:23:54 Age [y:d:h:m:s]: 00:203:12:15:26
Block: 1265412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143171 RingCT/type: yes/0
Extra: 01357819f46d5fc3efdc9c3ed7de1a9ba01d7a49032a1809863643974eef1a7a830211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d48b3f9cbbfd4154016cd26af668565812e2bb1b3d49b7fa1e265538983932bf 0.600000000000 1752619 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": 1265422, "vin": [ { "gen": { "height": 1265412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d48b3f9cbbfd4154016cd26af668565812e2bb1b3d49b7fa1e265538983932bf" } } ], "extra": [ 1, 53, 120, 25, 244, 109, 95, 195, 239, 220, 156, 62, 215, 222, 26, 155, 160, 29, 122, 73, 3, 42, 24, 9, 134, 54, 67, 151, 78, 239, 26, 122, 131, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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