Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1f11a1430ebcbe1bd78e102238bcf5dede00001fbb2703270fdeab6b1eb4a7

Tx prefix hash: 0543c73b631736c8b7930f8cb68c8f4498e3e3000e6f128534e919cdc568063a
Tx public key: d61d168ce90e078f3b51794063a61b17d3e5577e37a3d0b84bbf168853fc35a8
Timestamp: 1723419743 Timestamp [UCT]: 2024-08-11 23:42:23 Age [y:d:h:m:s]: 00:273:23:31:11
Block: 1085899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195723 RingCT/type: yes/0
Extra: 01d61d168ce90e078f3b51794063a61b17d3e5577e37a3d0b84bbf168853fc35a802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c9d21c4ed8b59b04c5970d83f8eee9948861b225d53092e5261e10f4bffe744 0.600000000000 1560490 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": 1085909, "vin": [ { "gen": { "height": 1085899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c9d21c4ed8b59b04c5970d83f8eee9948861b225d53092e5261e10f4bffe744" } } ], "extra": [ 1, 214, 29, 22, 140, 233, 14, 7, 143, 59, 81, 121, 64, 99, 166, 27, 23, 211, 229, 87, 126, 55, 163, 208, 184, 75, 191, 22, 136, 83, 252, 53, 168, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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