Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 345b6a86a007f21997fd10b4b28cb277842ffc5a97084fd97216e03a20b833e8

Tx prefix hash: 1a3c29c7547fdddc9ce96d3e8ccd623c1ff771ab3f3177ad21f0bac3ca6c8949
Tx public key: a1ec5e7b1cf144633d556b64be644567fe4c805429c2eab0a5664532dc4b698c
Timestamp: 1672756324 Timestamp [UCT]: 2023-01-03 14:32:04 Age [y:d:h:m:s]: 02:146:12:55:15
Block: 666745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626464 RingCT/type: yes/0
Extra: 01a1ec5e7b1cf144633d556b64be644567fe4c805429c2eab0a5664532dc4b698c02110000000352542ceb000000000000000000

1 output(s) for total of 3.791377234000 dcy

stealth address amount amount idx
00: 6b68cb778acc0b9553edd23311ab89cef59bf28fe575e8e76249184cf5bf5018 3.791377234000 1107882 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": 666755, "vin": [ { "gen": { "height": 666745 } } ], "vout": [ { "amount": 3791377234, "target": { "key": "6b68cb778acc0b9553edd23311ab89cef59bf28fe575e8e76249184cf5bf5018" } } ], "extra": [ 1, 161, 236, 94, 123, 28, 241, 68, 99, 61, 85, 107, 100, 190, 100, 69, 103, 254, 76, 128, 84, 41, 194, 234, 176, 165, 102, 69, 50, 220, 75, 105, 140, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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