Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28b65cbf21d97fa912d9c5451c661b8b5be2ee2e7e6edc2c44c9bf880c338951

Tx prefix hash: 11423042e40980c22c809779a2761ea06c364077915988d90c0cfcd1a68bfdfb
Tx public key: 642229ea5a08b2a0379491e49a31984e9631693aa5fc1cfc0ec8dfeba61894b4
Timestamp: 1720641714 Timestamp [UCT]: 2024-07-10 20:01:54 Age [y:d:h:m:s]: 00:268:17:57:01
Block: 1062878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192003 RingCT/type: yes/0
Extra: 01642229ea5a08b2a0379491e49a31984e9631693aa5fc1cfc0ec8dfeba61894b402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26bbe6ebe8459ab944fe7a64f1b2c8d61e0eb565e9cac8971da91bf256ec5b0e 0.600000000000 1533389 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": 1062888, "vin": [ { "gen": { "height": 1062878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26bbe6ebe8459ab944fe7a64f1b2c8d61e0eb565e9cac8971da91bf256ec5b0e" } } ], "extra": [ 1, 100, 34, 41, 234, 90, 8, 178, 160, 55, 148, 145, 228, 154, 49, 152, 78, 150, 49, 105, 58, 165, 252, 28, 252, 14, 200, 223, 235, 166, 24, 148, 180, 2, 17, 0, 0, 0, 5, 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