Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f629ea1f3b9af10c19be84f232ac4e807dddc4151e230741dbc4a571f7a30a0e

Tx prefix hash: 52fb6a51d42dbc8b8a3f5a0cf05b3b70d4da93cc9761c43b299b4b253bd87907
Tx public key: f6ec3819170d873e126da64b85aa47d627e81f4da339998694f9e9b8f4f21cd8
Timestamp: 1726555959 Timestamp [UCT]: 2024-09-17 06:52:39 Age [y:d:h:m:s]: 01:052:20:21:19
Block: 1111909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296175 RingCT/type: yes/0
Extra: 01f6ec3819170d873e126da64b85aa47d627e81f4da339998694f9e9b8f4f21cd802110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c99314e114bd0c786929ba2aa35458cec4506fd741cc74a7352d8f542af5f420 0.600000000000 1591034 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": 1111919, "vin": [ { "gen": { "height": 1111909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c99314e114bd0c786929ba2aa35458cec4506fd741cc74a7352d8f542af5f420" } } ], "extra": [ 1, 246, 236, 56, 25, 23, 13, 135, 62, 18, 109, 166, 75, 133, 170, 71, 214, 39, 232, 31, 77, 163, 57, 153, 134, 148, 249, 233, 184, 244, 242, 28, 216, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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