Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 211f4a0bd85d36b57c86ce0561f303e6bc65d4bb9cd0745ae0c7a1a1c019f364

Tx prefix hash: 4c3477a4ba6af97d4d5fe54eee5f5fe21eb3bbd5d1f9320ff4680d9bf38c6774
Tx public key: d9491e341b061b860ea81b45fa6fe55c4e2978c2011759149a65cdf203c8a965
Timestamp: 1721400387 Timestamp [UCT]: 2024-07-19 14:46:27 Age [y:d:h:m:s]: 00:256:14:57:54
Block: 1069174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183311 RingCT/type: yes/0
Extra: 01d9491e341b061b860ea81b45fa6fe55c4e2978c2011759149a65cdf203c8a965021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c9d1128486953cd795d96369b9962160cdb64bcb619999c2a1befb805f9505d 0.600000000000 1540497 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": 1069184, "vin": [ { "gen": { "height": 1069174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c9d1128486953cd795d96369b9962160cdb64bcb619999c2a1befb805f9505d" } } ], "extra": [ 1, 217, 73, 30, 52, 27, 6, 27, 134, 14, 168, 27, 69, 250, 111, 229, 92, 78, 41, 120, 194, 1, 23, 89, 20, 154, 101, 205, 242, 3, 200, 169, 101, 2, 17, 0, 0, 0, 7, 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