Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2e82f6e4feb2d7bd0aef06476d323df1ddc9b03bba6c8e020c737c122fae1b7

Tx prefix hash: fc5167ddcd4e9613f298bf70938f346df5df3f7c4a37766a50468d3affe9fe08
Tx public key: eada7815b6b59ce4287697e8fbfbcf9e92012bb28c570efd2f797c29b73c7d15
Timestamp: 1621801709 Timestamp [UCT]: 2021-05-23 20:28:29 Age [y:d:h:m:s]: 03:187:00:22:16
Block: 265823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 895827 RingCT/type: yes/0
Extra: 01eada7815b6b59ce4287697e8fbfbcf9e92012bb28c570efd2f797c29b73c7d15021100000013fdc4fdba000000000000000000

1 output(s) for total of 80.764143636000 dcy

stealth address amount amount idx
00: abaa83c7e2c25268742e4fefff1c56b3143dbd3a7dfc0b80734f76343b427a8d 80.764143636000 558695 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": 265833, "vin": [ { "gen": { "height": 265823 } } ], "vout": [ { "amount": 80764143636, "target": { "key": "abaa83c7e2c25268742e4fefff1c56b3143dbd3a7dfc0b80734f76343b427a8d" } } ], "extra": [ 1, 234, 218, 120, 21, 182, 181, 156, 228, 40, 118, 151, 232, 251, 251, 207, 158, 146, 1, 43, 178, 140, 87, 14, 253, 47, 121, 124, 41, 183, 60, 125, 21, 2, 17, 0, 0, 0, 19, 253, 196, 253, 186, 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