Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97eba8b8f54f2b248b1c32650ba8287dfbf5297b16afccb02f4a70db9a05f0fa

Tx prefix hash: dc9113c2fe79e44c8321d1e0874a1594e6fdd9d089778409865c195297cc1a87
Tx public key: b9e6a193ddea158f05c52ee887b242faf21c8ce71835d5837f26541112598a60
Timestamp: 1578904764 Timestamp [UCT]: 2020-01-13 08:39:24 Age [y:d:h:m:s]: 05:060:03:50:25
Block: 44445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193243 RingCT/type: yes/0
Extra: 01b9e6a193ddea158f05c52ee887b242faf21c8ce71835d5837f26541112598a600211000000024943cd9f000000000000000000

1 output(s) for total of 437.256330811000 dcy

stealth address amount amount idx
00: e3ca7b1c95b84f7888eb442b7ed5e657944e4eced2557205b2f6e98339b7f7e4 437.256330811000 80883 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": 44455, "vin": [ { "gen": { "height": 44445 } } ], "vout": [ { "amount": 437256330811, "target": { "key": "e3ca7b1c95b84f7888eb442b7ed5e657944e4eced2557205b2f6e98339b7f7e4" } } ], "extra": [ 1, 185, 230, 161, 147, 221, 234, 21, 143, 5, 197, 46, 232, 135, 178, 66, 250, 242, 28, 140, 231, 24, 53, 213, 131, 127, 38, 84, 17, 18, 89, 138, 96, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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