Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f2b17c4d557f521ae69c132049dffe8f844e461f83b14bd8321f1a9ab13a48

Tx prefix hash: 62e1b8e08a35c0117826fa8d92f11e993a304f0731b9ad5641d7aa7718f1fc93
Tx public key: a4737ae79185efbf9d1a4ab2c5f8905f6b84c5db1eceec74b371f73c04ee29a6
Timestamp: 1736056311 Timestamp [UCT]: 2025-01-05 05:51:51 Age [y:d:h:m:s]: 00:165:01:17:19
Block: 1190541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117642 RingCT/type: yes/0
Extra: 01a4737ae79185efbf9d1a4ab2c5f8905f6b84c5db1eceec74b371f73c04ee29a602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f1cd420ad6fcb5777d45bb9d287129d2386944e0cf9a56d1452ce5e201067d7 0.600000000000 1677058 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": 1190551, "vin": [ { "gen": { "height": 1190541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f1cd420ad6fcb5777d45bb9d287129d2386944e0cf9a56d1452ce5e201067d7" } } ], "extra": [ 1, 164, 115, 122, 231, 145, 133, 239, 191, 157, 26, 74, 178, 197, 248, 144, 95, 107, 132, 197, 219, 30, 206, 236, 116, 179, 113, 247, 60, 4, 238, 41, 166, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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