Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab56909c2b53424e0b50d5a1b64f67a6de246775a5a52033a4a326b7467de60f

Tx prefix hash: 78fad2226f582fc1310844c22b244292e8e4280e2b684cf45acb4350fb136b01
Tx public key: 98926bb2b7a0e3bc69ecc6bbc411971d819779af41419d496b9f1e95a71062ae
Timestamp: 1589363166 Timestamp [UCT]: 2020-05-13 09:46:06 Age [y:d:h:m:s]: 04:349:10:14:36
Block: 100422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169666 RingCT/type: yes/0
Extra: 0198926bb2b7a0e3bc69ecc6bbc411971d819779af41419d496b9f1e95a71062ae0211000001f0a86a1a65000000000000000000

1 output(s) for total of 285.273209438000 dcy

stealth address amount amount idx
00: 9d659fb9cc868968f76ccafe95a8b2bda83c543f906a3fe074e12e6e4d085b95 285.273209438000 176942 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": 100432, "vin": [ { "gen": { "height": 100422 } } ], "vout": [ { "amount": 285273209438, "target": { "key": "9d659fb9cc868968f76ccafe95a8b2bda83c543f906a3fe074e12e6e4d085b95" } } ], "extra": [ 1, 152, 146, 107, 178, 183, 160, 227, 188, 105, 236, 198, 187, 196, 17, 151, 29, 129, 151, 121, 175, 65, 65, 157, 73, 107, 159, 30, 149, 167, 16, 98, 174, 2, 17, 0, 0, 1, 240, 168, 106, 26, 101, 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