Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 815238d4542708d5ca0b2ae279aaf423a8113380d9b1db197a31ae7d73a49c11

Tx prefix hash: 471c89c4f4045f64c9e6a6092cc25f03ca6740b16ad9e04716158aa3a23dd209
Tx public key: a168392081aa5474fe812bc7e929f311ea3fd2989d239a066776e04ff86b0a3d
Timestamp: 1710699072 Timestamp [UCT]: 2024-03-17 18:11:12 Age [y:d:h:m:s]: 00:311:20:20:14
Block: 980467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223163 RingCT/type: yes/0
Extra: 01a168392081aa5474fe812bc7e929f311ea3fd2989d239a066776e04ff86b0a3d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a220fddf520a562ca3146f59b59858828350761ac464fb53b26ab57412e1ee54 0.600000000000 1440534 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": 980477, "vin": [ { "gen": { "height": 980467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a220fddf520a562ca3146f59b59858828350761ac464fb53b26ab57412e1ee54" } } ], "extra": [ 1, 161, 104, 57, 32, 129, 170, 84, 116, 254, 129, 43, 199, 233, 41, 243, 17, 234, 63, 210, 152, 157, 35, 154, 6, 103, 118, 224, 79, 248, 107, 10, 61, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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