Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abea4fe2e996244d8f0fe0cb4deb42519211bb35c2db32a9f08759cf5e584379

Tx prefix hash: db3f53e1b7b0b4e27039a80f991ac59ad189b299532b4a50fbea5e6b2298b644
Tx public key: 21ba1bccbd5a040caa9af7b62733deeb3e568c2b2c9120e01a5d3d9a47cad7fa
Timestamp: 1703429889 Timestamp [UCT]: 2023-12-24 14:58:09 Age [y:d:h:m:s]: 01:173:20:23:55
Block: 920181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385320 RingCT/type: yes/0
Extra: 0121ba1bccbd5a040caa9af7b62733deeb3e568c2b2c9120e01a5d3d9a47cad7fa02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea6967c8031f964edfd5baf8d7ffb6753cb4f89fa723ff9a95a2b966ec9d5373 0.600000000000 1377859 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": 920191, "vin": [ { "gen": { "height": 920181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea6967c8031f964edfd5baf8d7ffb6753cb4f89fa723ff9a95a2b966ec9d5373" } } ], "extra": [ 1, 33, 186, 27, 204, 189, 90, 4, 12, 170, 154, 247, 182, 39, 51, 222, 235, 62, 86, 140, 43, 44, 145, 32, 224, 26, 93, 61, 154, 71, 202, 215, 250, 2, 17, 0, 0, 0, 2, 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