Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eff23c7f5f08fad24e52ea1253c45385aaef4138230710c2e4baaaff9ee37da

Tx prefix hash: f1500e26e18dc8cc5dc09828353946685784c935c860024660b4d14e9538cae4
Tx public key: 7a72068308346658bf3fdc4c9b23b8b62880b9d0229a41fbe186543a59dd6e5b
Timestamp: 1739690180 Timestamp [UCT]: 2025-02-16 07:16:20 Age [y:d:h:m:s]: 00:344:10:50:43
Block: 1220321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243886 RingCT/type: yes/0
Extra: 017a72068308346658bf3fdc4c9b23b8b62880b9d0229a41fbe186543a59dd6e5b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2660ab17104e45dc3a3d61a4847b0b49adc93cf24ca9a9c5bf4e570e5a0da59 0.600000000000 1707160 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": 1220331, "vin": [ { "gen": { "height": 1220321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2660ab17104e45dc3a3d61a4847b0b49adc93cf24ca9a9c5bf4e570e5a0da59" } } ], "extra": [ 1, 122, 114, 6, 131, 8, 52, 102, 88, 191, 63, 220, 76, 155, 35, 184, 182, 40, 128, 185, 208, 34, 154, 65, 251, 225, 134, 84, 58, 89, 221, 110, 91, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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