Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9f59b5ae7e93371adecc02c212d8d810bb9068c8273d91cfa1830d68999096f

Tx prefix hash: 57cda2d75c0a82c2e82d0848832e851e2f6b0673cc1f85529b30018a7ead8c28
Tx public key: dcf5fb00eef5d5f0afa5b85bd85564060b249e711f13bc2abffce06af3007f7c
Timestamp: 1721762721 Timestamp [UCT]: 2024-07-23 19:25:21 Age [y:d:h:m:s]: 00:267:10:04:54
Block: 1072164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191041 RingCT/type: yes/0
Extra: 01dcf5fb00eef5d5f0afa5b85bd85564060b249e711f13bc2abffce06af3007f7c02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e213b8be033ff7f77a19477d27816fd3b2f96fa28414eaf3363e06e3434fae98 0.600000000000 1544617 of 15

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": 1072174, "vin": [ { "gen": { "height": 1072164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e213b8be033ff7f77a19477d27816fd3b2f96fa28414eaf3363e06e3434fae98" } } ], "extra": [ 1, 220, 245, 251, 0, 238, 245, 213, 240, 175, 165, 184, 91, 216, 85, 100, 6, 11, 36, 158, 113, 31, 19, 188, 42, 191, 252, 224, 106, 243, 0, 127, 124, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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