Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c38a18cf1123f9601ac8134a53fd60c695147a170a4a39a8171613aa77e5c60b

Tx prefix hash: 873e087f061740615a7044fc407b799403cd50f6ceb0e90ebca8e0ac53c4aa37
Tx public key: ff1243a4b66c0e30700f3bc63b5d225e11c27a3489ed5ce416ca8987e5f32791
Timestamp: 1721361227 Timestamp [UCT]: 2024-07-19 03:53:47 Age [y:d:h:m:s]: 00:258:16:29:27
Block: 1068853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184786 RingCT/type: yes/0
Extra: 01ff1243a4b66c0e30700f3bc63b5d225e11c27a3489ed5ce416ca8987e5f3279102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fa7b9e9efa1b50ac15b325018775b468c4c1e391aafa8bf8e0bd682d6e7c31b 0.600000000000 1540046 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": 1068863, "vin": [ { "gen": { "height": 1068853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fa7b9e9efa1b50ac15b325018775b468c4c1e391aafa8bf8e0bd682d6e7c31b" } } ], "extra": [ 1, 255, 18, 67, 164, 182, 108, 14, 48, 112, 15, 59, 198, 59, 93, 34, 94, 17, 194, 122, 52, 137, 237, 92, 228, 22, 202, 137, 135, 229, 243, 39, 145, 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