Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0db0d2046ab70a761a96f8ed95b28a32ef4adcaa2d5465398cef79b60adc8bf

Tx prefix hash: 7e278cbdcc898b58e42873fe6e920a669e57f32b44078c5898cb345399102c54
Tx public key: af5120b9165c2c805ea303316c0f1e3f848be023e6ba095498be4e45188b4ff2
Timestamp: 1710053445 Timestamp [UCT]: 2024-03-10 06:50:45 Age [y:d:h:m:s]: 01:255:21:12:08
Block: 975104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441587 RingCT/type: yes/0
Extra: 01af5120b9165c2c805ea303316c0f1e3f848be023e6ba095498be4e45188b4ff202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f6440b3ac22ffdc5daa0f12ee7f11a01b06dff3e65a4f1d4bb16644d5153d30 0.600000000000 1435075 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": 975114, "vin": [ { "gen": { "height": 975104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f6440b3ac22ffdc5daa0f12ee7f11a01b06dff3e65a4f1d4bb16644d5153d30" } } ], "extra": [ 1, 175, 81, 32, 185, 22, 92, 44, 128, 94, 163, 3, 49, 108, 15, 30, 63, 132, 139, 224, 35, 230, 186, 9, 84, 152, 190, 78, 69, 24, 139, 79, 242, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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