Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b32847afd3202c3f64dd4c4f07892c8d24fef31f77145394090551086e575f

Tx prefix hash: fe50bbcad81189e44d4f4ed5011dc3015d39b45a9bd8764b2ad52bfb23f9b40b
Tx public key: 347e0e8ea4800a0308471819d5c5683adfc7b2c30cbe554533e6204b73953bda
Timestamp: 1731025456 Timestamp [UCT]: 2024-11-08 00:24:16 Age [y:d:h:m:s]: 00:222:00:39:23
Block: 1148881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158432 RingCT/type: yes/0
Extra: 01347e0e8ea4800a0308471819d5c5683adfc7b2c30cbe554533e6204b73953bda0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51e6d9f0a3a355159bce28a9e130f3b4abe6874a75f0b865e6bdcaa887d7ba5f 0.600000000000 1633834 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": 1148891, "vin": [ { "gen": { "height": 1148881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51e6d9f0a3a355159bce28a9e130f3b4abe6874a75f0b865e6bdcaa887d7ba5f" } } ], "extra": [ 1, 52, 126, 14, 142, 164, 128, 10, 3, 8, 71, 24, 25, 213, 197, 104, 58, 223, 199, 178, 195, 12, 190, 85, 69, 51, 230, 32, 75, 115, 149, 59, 218, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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