Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71002e6c7c07f77bccbe3101e8ffc47e699cdde26a802d03848e1a3ae0057b37

Tx prefix hash: 35f888bde26805869017b5205e6a87a43600fd1bc1f1f8520781aba1e0c49c33
Tx public key: 4402f398b4943f4315aa03089c44752c1ee6f2595fcba5cced4847c3e1f1a1fd
Timestamp: 1715960977 Timestamp [UCT]: 2024-05-17 15:49:37 Age [y:d:h:m:s]: 00:322:14:13:38
Block: 1024072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230572 RingCT/type: yes/0
Extra: 014402f398b4943f4315aa03089c44752c1ee6f2595fcba5cced4847c3e1f1a1fd02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2f0e41af1a15940824b9534f96a01417817657e986e5d738b11d758ec71c99c 0.600000000000 1489529 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": 1024082, "vin": [ { "gen": { "height": 1024072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2f0e41af1a15940824b9534f96a01417817657e986e5d738b11d758ec71c99c" } } ], "extra": [ 1, 68, 2, 243, 152, 180, 148, 63, 67, 21, 170, 3, 8, 156, 68, 117, 44, 30, 230, 242, 89, 95, 203, 165, 204, 237, 72, 71, 195, 225, 241, 161, 253, 2, 17, 0, 0, 0, 10, 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