Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43aec7ccafbd0a5612cb0b37871b49bcb93c558fb47f1e59d0004af08f48a926

Tx prefix hash: 1e7962e6fd9bcd75912e97c9decf8de4f5073c501e398b8280e047e85585a337
Tx public key: 690acec9bbba9c4ce1d5493b1635f1e871b244ca139683dc0f9589a76ba83caf
Timestamp: 1694870384 Timestamp [UCT]: 2023-09-16 13:19:44 Age [y:d:h:m:s]: 01:130:22:07:55
Block: 849406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354843 RingCT/type: yes/0
Extra: 01690acec9bbba9c4ce1d5493b1635f1e871b244ca139683dc0f9589a76ba83caf021100000003faf35c9c000000000000000000

1 output(s) for total of 0.940947460000 dcy

stealth address amount amount idx
00: 73f8533de1f77859a7cf5bbc6fc726206b2edb91f8c3f6aa8c37de5caec22aa7 0.940947460000 1303070 of 0

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": 849416, "vin": [ { "gen": { "height": 849406 } } ], "vout": [ { "amount": 940947460, "target": { "key": "73f8533de1f77859a7cf5bbc6fc726206b2edb91f8c3f6aa8c37de5caec22aa7" } } ], "extra": [ 1, 105, 10, 206, 201, 187, 186, 156, 76, 225, 213, 73, 59, 22, 53, 241, 232, 113, 178, 68, 202, 19, 150, 131, 220, 15, 149, 137, 167, 107, 168, 60, 175, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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