Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53dc36d0dff552401746f922a49c8b78f3421d025f26b42b30ed52482e988d58

Tx prefix hash: 13c9c6117414b8a9e2f64cfaac8d188a3d5809014c8c8edc8994d22906d31d23
Tx public key: f61492910ac66c3a0f85a55f7029811dd2c25e320d4d85c99f43d66e43c0742f
Timestamp: 1703440228 Timestamp [UCT]: 2023-12-24 17:50:28 Age [y:d:h:m:s]: 01:025:08:59:21
Block: 920263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279478 RingCT/type: yes/0
Extra: 01f61492910ac66c3a0f85a55f7029811dd2c25e320d4d85c99f43d66e43c0742f021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13cfe51ff71391d7bf522a25f42bfea7f89b968f002999b12a62c5e36c9d0628 0.600000000000 1377941 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": 920273, "vin": [ { "gen": { "height": 920263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13cfe51ff71391d7bf522a25f42bfea7f89b968f002999b12a62c5e36c9d0628" } } ], "extra": [ 1, 246, 20, 146, 145, 10, 198, 108, 58, 15, 133, 165, 95, 112, 41, 129, 29, 210, 194, 94, 50, 13, 77, 133, 201, 159, 67, 214, 110, 67, 192, 116, 47, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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