Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab20e2ef3450b9aee8c27392219d53a84d970c2d5ec598e48083434497e6d692

Tx prefix hash: e61924332616cbe8e920bba4aa2cf73f76c2d142b0a027b38ad18913b20ef409
Tx public key: bea0521eba81d970fb66e0f82d5f7e21774243d159afce3457206f752584eadb
Timestamp: 1637789443 Timestamp [UCT]: 2021-11-24 21:30:43 Age [y:d:h:m:s]: 03:110:18:12:24
Block: 381374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 857847 RingCT/type: yes/0
Extra: 01bea0521eba81d970fb66e0f82d5f7e21774243d159afce3457206f752584eadb021100000010f6cc1430000000000000000000

1 output(s) for total of 33.446447861000 dcy

stealth address amount amount idx
00: 620d7e0c7c6d799fe2f224b6c9f67036eff9dc2939e488a5f9fb29db2b4d678e 33.446447861000 770464 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": 381384, "vin": [ { "gen": { "height": 381374 } } ], "vout": [ { "amount": 33446447861, "target": { "key": "620d7e0c7c6d799fe2f224b6c9f67036eff9dc2939e488a5f9fb29db2b4d678e" } } ], "extra": [ 1, 190, 160, 82, 30, 186, 129, 217, 112, 251, 102, 224, 248, 45, 95, 126, 33, 119, 66, 67, 209, 89, 175, 206, 52, 87, 32, 111, 117, 37, 132, 234, 219, 2, 17, 0, 0, 0, 16, 246, 204, 20, 48, 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