Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ac1b415d141824af4264e35129b55e32db96bd85200f1dc5941829876d4139

Tx prefix hash: b12edbbc39966d41d1b9cb9885c0b6b9f1f2bdbff6abdba4466120001c3354e2
Tx public key: 0e5f7f29273e69159f3f0bfc3cf76757a14fd50170b117c47f0b88576ad1a1c7
Timestamp: 1740542889 Timestamp [UCT]: 2025-02-26 04:08:09 Age [y:d:h:m:s]: 00:262:22:20:01
Block: 1227402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185677 RingCT/type: yes/0
Extra: 010e5f7f29273e69159f3f0bfc3cf76757a14fd50170b117c47f0b88576ad1a1c7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c20eb39dcbf9e11148a2db0711aece974c3689036e4c6d9a752b892442e1c672 0.600000000000 1714275 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": 1227412, "vin": [ { "gen": { "height": 1227402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c20eb39dcbf9e11148a2db0711aece974c3689036e4c6d9a752b892442e1c672" } } ], "extra": [ 1, 14, 95, 127, 41, 39, 62, 105, 21, 159, 63, 11, 252, 60, 247, 103, 87, 161, 79, 213, 1, 112, 177, 23, 196, 127, 11, 136, 87, 106, 209, 161, 199, 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