Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6415dde0ab54e6af205498e3b994de217742a33075f6c553dade5fd713aa68c0

Tx prefix hash: 767da28dae9267ced18f26a5bd4ae417a8ed1042e47143e0a7551bee6fda4e42
Tx public key: ecadce81bdd7acc0c08ecf1cec13957dd129f8b8c32cd8d7dedfef70c0aef618
Timestamp: 1723381326 Timestamp [UCT]: 2024-08-11 13:02:06 Age [y:d:h:m:s]: 00:237:10:28:06
Block: 1085594 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169571 RingCT/type: yes/0
Extra: 01ecadce81bdd7acc0c08ecf1cec13957dd129f8b8c32cd8d7dedfef70c0aef61802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb6f2dfc8bfe8067fe5a34ff3a5f9d3388d945b020c4449feb75d10392f7a2d0 0.600000000000 1560181 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": 1085604, "vin": [ { "gen": { "height": 1085594 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb6f2dfc8bfe8067fe5a34ff3a5f9d3388d945b020c4449feb75d10392f7a2d0" } } ], "extra": [ 1, 236, 173, 206, 129, 189, 215, 172, 192, 192, 142, 207, 28, 236, 19, 149, 125, 209, 41, 248, 184, 195, 44, 216, 215, 222, 223, 239, 112, 192, 174, 246, 24, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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