Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a16f40c5e6b84dbbf81ef1b73a6a72793127482fb378df431374a60b694e0f

Tx prefix hash: fbf3e3ee211c83b78d4f38371abe86c799ee852565c0e6e03c47bf5b0d061e02
Tx public key: c70459aaf4806a9129a33c5729259086b27339e5e8454a661c8fdbe7ee23a9a6
Timestamp: 1646638977 Timestamp [UCT]: 2022-03-07 07:42:57 Age [y:d:h:m:s]: 02:263:07:26:45
Block: 453123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 707646 RingCT/type: yes/0
Extra: 01c70459aaf4806a9129a33c5729259086b27339e5e8454a661c8fdbe7ee23a9a60211000000084da16a3a000000000000000000

1 output(s) for total of 19.347091022000 dcy

stealth address amount amount idx
00: 5246abd24d32ff070df19ee3f9797a9e9ce288d66ecd47efafd6273abdf48132 19.347091022000 868540 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": 453133, "vin": [ { "gen": { "height": 453123 } } ], "vout": [ { "amount": 19347091022, "target": { "key": "5246abd24d32ff070df19ee3f9797a9e9ce288d66ecd47efafd6273abdf48132" } } ], "extra": [ 1, 199, 4, 89, 170, 244, 128, 106, 145, 41, 163, 60, 87, 41, 37, 144, 134, 178, 115, 57, 229, 232, 69, 74, 102, 28, 143, 219, 231, 238, 35, 169, 166, 2, 17, 0, 0, 0, 8, 77, 161, 106, 58, 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