Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583d5bd9a880736e5616fa1d22eb07ad8b21337cd9bbf0fec227e2779c5fa096

Tx prefix hash: 4e4f0fef980b104be37fd8f824965fe83290fcfd3c3f3865ffdf41eb0e9dc48c
Tx public key: 0a903b32afc615f45997b2caf4b012faf248d92f8430404efcf0ea8db28d58a2
Timestamp: 1736601694 Timestamp [UCT]: 2025-01-11 13:21:34 Age [y:d:h:m:s]: 00:344:03:16:54
Block: 1195046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243518 RingCT/type: yes/0
Extra: 010a903b32afc615f45997b2caf4b012faf248d92f8430404efcf0ea8db28d58a20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd9c08afeb68a690c7ce1d2e34d8e29d079c29399f1cd479303cf6c01ac98b02 0.600000000000 1681631 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": 1195056, "vin": [ { "gen": { "height": 1195046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd9c08afeb68a690c7ce1d2e34d8e29d079c29399f1cd479303cf6c01ac98b02" } } ], "extra": [ 1, 10, 144, 59, 50, 175, 198, 21, 244, 89, 151, 178, 202, 244, 176, 18, 250, 242, 72, 217, 47, 132, 48, 64, 78, 252, 240, 234, 141, 178, 141, 88, 162, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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