Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf3961f3a8f42a1406eaab8ca8453c09d42a1cd5ca55dbf0ca13ddc5d8056d6

Tx prefix hash: 7599763dae53084a2adf77256dbf89584d2aa06b57b0ba73b102476134f1f3a7
Tx public key: 03210327f4a1b1dca68d4e4f3d6076e135d0ae0a90453a98438a88a3762e7fcf
Timestamp: 1738681547 Timestamp [UCT]: 2025-02-04 15:05:47 Age [y:d:h:m:s]: 00:035:20:39:43
Block: 1211992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25676 RingCT/type: yes/0
Extra: 0103210327f4a1b1dca68d4e4f3d6076e135d0ae0a90453a98438a88a3762e7fcf021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e5be4ba5f82195dc8827830da85949da997bcd1ce1c36223df2c10000524b8 0.600000000000 1698759 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": 1212002, "vin": [ { "gen": { "height": 1211992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e5be4ba5f82195dc8827830da85949da997bcd1ce1c36223df2c10000524b8" } } ], "extra": [ 1, 3, 33, 3, 39, 244, 161, 177, 220, 166, 141, 78, 79, 61, 96, 118, 225, 53, 208, 174, 10, 144, 69, 58, 152, 67, 138, 136, 163, 118, 46, 127, 207, 2, 17, 0, 0, 0, 7, 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