Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58362dceed171d75dd38d9920419a9a62ad0aae1864f124892a1c7350256b62f

Tx prefix hash: 672a105cf855ea158df2e56a96f8669e4ee61c9bd07a6989581cf6d491dadcfb
Tx public key: a296541e74db3d8c39a536b36d1e794fa9246e1c8da8cc289f344ca975b95dc9
Timestamp: 1727041475 Timestamp [UCT]: 2024-09-22 21:44:35 Age [y:d:h:m:s]: 00:207:16:58:03
Block: 1115934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148274 RingCT/type: yes/0
Extra: 01a296541e74db3d8c39a536b36d1e794fa9246e1c8da8cc289f344ca975b95dc9021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f74d56eebb0e439775e15e2ab5c8ce8bf16b2a08d0235b0ad4e0dfb0dffcca9a 0.600000000000 1596241 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": 1115944, "vin": [ { "gen": { "height": 1115934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f74d56eebb0e439775e15e2ab5c8ce8bf16b2a08d0235b0ad4e0dfb0dffcca9a" } } ], "extra": [ 1, 162, 150, 84, 30, 116, 219, 61, 140, 57, 165, 54, 179, 109, 30, 121, 79, 169, 36, 110, 28, 141, 168, 204, 40, 159, 52, 76, 169, 117, 185, 93, 201, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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