Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 367a7895acada0c1a9f5376fe1ee20d834993fe26564a471af9fcf9b6ae6cb84

Tx prefix hash: 2106d31255529abf61cad739e0a857ab5274451b279b8aa78dad19d49bf0cc9f
Tx public key: e9a460ac9eb53932ba0df1f7370b9a58367394c5c6dff48538ce5c9d2da5fa2c
Timestamp: 1713583832 Timestamp [UCT]: 2024-04-20 03:30:32 Age [y:d:h:m:s]: 00:201:21:41:53
Block: 1004344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144555 RingCT/type: yes/0
Extra: 01e9a460ac9eb53932ba0df1f7370b9a58367394c5c6dff48538ce5c9d2da5fa2c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c61c7be06d7d6090f62aa4723b01ce2e3face27aa96963d5cbcb605eca8ec4 0.600000000000 1464912 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": 1004354, "vin": [ { "gen": { "height": 1004344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c61c7be06d7d6090f62aa4723b01ce2e3face27aa96963d5cbcb605eca8ec4" } } ], "extra": [ 1, 233, 164, 96, 172, 158, 181, 57, 50, 186, 13, 241, 247, 55, 11, 154, 88, 54, 115, 148, 197, 198, 223, 244, 133, 56, 206, 92, 157, 45, 165, 250, 44, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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