Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56f03ab8203b11d29d1f6593d232b89f9a97f64c48fd48c36fab8422356a7cee

Tx prefix hash: 9fcf3fc22191710633ff5dc978edf063e54a05166b6c579827881c8bc27ca417
Tx public key: 73c0c79126b1871850bff5c48853b6ef4c73c6e61d8bfe61ef1e0c962e78e926
Timestamp: 1762356880 Timestamp [UCT]: 2025-11-05 15:34:40 Age [y:d:h:m:s]: 00:062:20:38:18
Block: 1405583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45024 RingCT/type: yes/0
Extra: 0173c0c79126b1871850bff5c48853b6ef4c73c6e61d8bfe61ef1e0c962e78e926021100000005df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7778ac0088882326fbdbcffc06f67afeb0c5f94ae15d692d09e833b36a648086 0.600000000000 1893964 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": 1405593, "vin": [ { "gen": { "height": 1405583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7778ac0088882326fbdbcffc06f67afeb0c5f94ae15d692d09e833b36a648086" } } ], "extra": [ 1, 115, 192, 199, 145, 38, 177, 135, 24, 80, 191, 245, 196, 136, 83, 182, 239, 76, 115, 198, 230, 29, 139, 254, 97, 239, 30, 12, 150, 46, 120, 233, 38, 2, 17, 0, 0, 0, 5, 223, 90, 36, 122, 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