Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf32ed4d7114ad18dbe4e6d526d568879f91eca4dad589e410e5dcd7be118c01

Tx prefix hash: 667b923d267aea8451a020badd3230a3f5d8dbb22d7237a2f7bb24dc5de689e5
Tx public key: e3b337db1b88d84c90b61d3123d0d8baa525d4c21df75c0ccf0887f65b3f878e
Timestamp: 1760864231 Timestamp [UCT]: 2025-10-19 08:57:11 Age [y:d:h:m:s]: 00:076:01:34:57
Block: 1393242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54454 RingCT/type: yes/0
Extra: 01e3b337db1b88d84c90b61d3123d0d8baa525d4c21df75c0ccf0887f65b3f878e021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2bb18dd9b05fd44dd313c2dd3c177a5bd49d9f0c7be042b34a44f781ac1ec00 0.600000000000 1881501 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": 1393252, "vin": [ { "gen": { "height": 1393242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2bb18dd9b05fd44dd313c2dd3c177a5bd49d9f0c7be042b34a44f781ac1ec00" } } ], "extra": [ 1, 227, 179, 55, 219, 27, 136, 216, 76, 144, 182, 29, 49, 35, 208, 216, 186, 165, 37, 212, 194, 29, 247, 92, 12, 207, 8, 135, 246, 91, 63, 135, 142, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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