Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d026e50d4a822b38b0e6df513cddce1af8a9205825fea8c8c68c7a0119411b55

Tx prefix hash: dca19032a088315e67f27f7191ddbc26fae2e97ef61b980a68149932b05140ad
Tx public key: a4ddbf4e5a2389ee724a3a002374378732786ee55e7561e1fb3f948e1889a8cb
Timestamp: 1723491924 Timestamp [UCT]: 2024-08-12 19:45:24 Age [y:d:h:m:s]: 00:236:15:48:35
Block: 1086507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169015 RingCT/type: yes/0
Extra: 01a4ddbf4e5a2389ee724a3a002374378732786ee55e7561e1fb3f948e1889a8cb021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d84deb05802c56170b14699a557ed3f60ca3ad08674e02ca90ddf2106efd8a9 0.600000000000 1561104 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": 1086517, "vin": [ { "gen": { "height": 1086507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d84deb05802c56170b14699a557ed3f60ca3ad08674e02ca90ddf2106efd8a9" } } ], "extra": [ 1, 164, 221, 191, 78, 90, 35, 137, 238, 114, 74, 58, 0, 35, 116, 55, 135, 50, 120, 110, 229, 94, 117, 97, 225, 251, 63, 148, 142, 24, 137, 168, 203, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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