Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b26612d89e6db3da63eafeb1ca35df22d04b1e79d27d2358f11c7aab40012a68

Tx prefix hash: 4edd085ab6eb3bc8f2b2f00ef5b34e654171b115a73b5257ba46952e7728b9ac
Tx public key: 5680d741af9cdadf384e74bdf6d1f2f627ceefce12e7b9e7a06a767f768afd5c
Timestamp: 1581822888 Timestamp [UCT]: 2020-02-16 03:14:48 Age [y:d:h:m:s]: 05:057:17:29:13
Block: 65841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1194249 RingCT/type: yes/0
Extra: 015680d741af9cdadf384e74bdf6d1f2f627ceefce12e7b9e7a06a767f768afd5c0211000000017adf42d3000000000000000000

1 output(s) for total of 371.400295439000 dcy

stealth address amount amount idx
00: cd8d4f7d4667021e6b6ae4078c1ef78acc8e80074db1219ecab2a45f84cbb9b6 371.400295439000 121454 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": 65851, "vin": [ { "gen": { "height": 65841 } } ], "vout": [ { "amount": 371400295439, "target": { "key": "cd8d4f7d4667021e6b6ae4078c1ef78acc8e80074db1219ecab2a45f84cbb9b6" } } ], "extra": [ 1, 86, 128, 215, 65, 175, 156, 218, 223, 56, 78, 116, 189, 246, 209, 242, 246, 39, 206, 239, 206, 18, 231, 185, 231, 160, 106, 118, 127, 118, 138, 253, 92, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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