Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e332feeecec94177c5c0455cbcddbe71bd61844624829c82ffa4db8c164382f3

Tx prefix hash: dd158e080a13abeeaa5ff6bdeadb919ec7aeb84bd938acfb6a8b806afed85797
Tx public key: 88f1760647a78471ad9e3e540670a76469fa1d1fc1a44a3fc4cd21eae39013fa
Timestamp: 1709154446 Timestamp [UCT]: 2024-02-28 21:07:26 Age [y:d:h:m:s]: 01:049:12:05:14
Block: 967647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296395 RingCT/type: yes/0
Extra: 0188f1760647a78471ad9e3e540670a76469fa1d1fc1a44a3fc4cd21eae39013fa02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1602b4327c2a4f978d5c9df941202f74666bea2dbd8633ee76f8e0ef5f7be1b9 0.600000000000 1427430 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": 967657, "vin": [ { "gen": { "height": 967647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1602b4327c2a4f978d5c9df941202f74666bea2dbd8633ee76f8e0ef5f7be1b9" } } ], "extra": [ 1, 136, 241, 118, 6, 71, 167, 132, 113, 173, 158, 62, 84, 6, 112, 167, 100, 105, 250, 29, 31, 193, 164, 74, 63, 196, 205, 33, 234, 227, 144, 19, 250, 2, 17, 0, 0, 0, 2, 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