Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46922af3a0cc4a5a9d4304b726ba7b6d0eecbf93c666f701bb0cf863e327385a

Tx prefix hash: d7290d7d58d47ddac930dd737dfe59b52ae9fc803af31e4fd732ee3968df0b9c
Tx public key: d84b10a2037337f5992b8bc1721dc1e5a1c4bda23fd61c4a790dab988ea8cf12
Timestamp: 1703625012 Timestamp [UCT]: 2023-12-26 21:10:12 Age [y:d:h:m:s]: 01:112:14:08:30
Block: 921802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341577 RingCT/type: yes/0
Extra: 01d84b10a2037337f5992b8bc1721dc1e5a1c4bda23fd61c4a790dab988ea8cf1202110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44beb137a4bb2e56d18c0e00fc0ec0eb22cbe2a53d4de4a269fa8c0fa085c39b 0.600000000000 1379496 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": 921812, "vin": [ { "gen": { "height": 921802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44beb137a4bb2e56d18c0e00fc0ec0eb22cbe2a53d4de4a269fa8c0fa085c39b" } } ], "extra": [ 1, 216, 75, 16, 162, 3, 115, 55, 245, 153, 43, 139, 193, 114, 29, 193, 229, 161, 196, 189, 162, 63, 214, 28, 74, 121, 13, 171, 152, 142, 168, 207, 18, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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