Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75b8eb4e1e30813254b7298c566233a01d2888baafa50a425c4fc5bf4e20bf6a

Tx prefix hash: c60d48b966bf1b95684560e8daedb84e5aef84ee802f9fb20ce5804c4cb63d11
Tx public key: a28c8c4009e48058f1241696575138efc291d68bcb6ffb6ff1e2e9d8b877f8be
Timestamp: 1736945565 Timestamp [UCT]: 2025-01-15 12:52:45 Age [y:d:h:m:s]: 00:153:18:33:38
Block: 1197895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109603 RingCT/type: yes/0
Extra: 01a28c8c4009e48058f1241696575138efc291d68bcb6ffb6ff1e2e9d8b877f8be021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe4af2c98313422b34c1e9d1a4e1f09712987096304dc372eb9fbae67127d849 0.600000000000 1684512 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": 1197905, "vin": [ { "gen": { "height": 1197895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe4af2c98313422b34c1e9d1a4e1f09712987096304dc372eb9fbae67127d849" } } ], "extra": [ 1, 162, 140, 140, 64, 9, 228, 128, 88, 241, 36, 22, 150, 87, 81, 56, 239, 194, 145, 214, 139, 203, 111, 251, 111, 241, 226, 233, 216, 184, 119, 248, 190, 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