Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4a3b7a0986905bcda2f6687039ea580974f999fd2192483d17643d05cf9a923

Tx prefix hash: 531d83b7b003612bdf2300b3d547d055487f9974857fc19b27569d65838a1690
Tx public key: 023165dbbab0b4c1d2d6190e36995cbe6537f118b1c2fa9b8471eab01f328660
Timestamp: 1588732659 Timestamp [UCT]: 2020-05-06 02:37:39 Age [y:d:h:m:s]: 05:034:10:11:05
Block: 98561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202079 RingCT/type: yes/0
Extra: 01023165dbbab0b4c1d2d6190e36995cbe6537f118b1c2fa9b8471eab01f3286600211000000026fa03929000000000000000000

1 output(s) for total of 289.352511583000 dcy

stealth address amount amount idx
00: 52158f0bae0ad1ac846ce860d15cf3c0d76be6e61602c2f9009c39f0dc9d9e50 289.352511583000 174235 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": 98571, "vin": [ { "gen": { "height": 98561 } } ], "vout": [ { "amount": 289352511583, "target": { "key": "52158f0bae0ad1ac846ce860d15cf3c0d76be6e61602c2f9009c39f0dc9d9e50" } } ], "extra": [ 1, 2, 49, 101, 219, 186, 176, 180, 193, 210, 214, 25, 14, 54, 153, 92, 190, 101, 55, 241, 24, 177, 194, 250, 155, 132, 113, 234, 176, 31, 50, 134, 96, 2, 17, 0, 0, 0, 2, 111, 160, 57, 41, 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