Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75d7cfad4bdbfc541504a8c7f4fa3e4b6d776861864951db3a844524b0018a0

Tx prefix hash: bfe910d966bbf3dfc8728831ef7c97d73121728d1ea41584b1076f7c5df2445e
Tx public key: 4e7791058d124dc906a1bdd9efb04251cb4954670725fccd9c64ab6e1c7af34e
Timestamp: 1697274104 Timestamp [UCT]: 2023-10-14 09:01:44 Age [y:d:h:m:s]: 01:098:08:12:17
Block: 869347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331504 RingCT/type: yes/0
Extra: 014e7791058d124dc906a1bdd9efb04251cb4954670725fccd9c64ab6e1c7af34e0211000000014b8f5122000000000000000000

1 output(s) for total of 0.808151036000 dcy

stealth address amount amount idx
00: b7a08962f7d70313ba07c2e413f1ef5a065d75a0ee8c005dfa7b365908a5e8cd 0.808151036000 1324190 of 0

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": 869357, "vin": [ { "gen": { "height": 869347 } } ], "vout": [ { "amount": 808151036, "target": { "key": "b7a08962f7d70313ba07c2e413f1ef5a065d75a0ee8c005dfa7b365908a5e8cd" } } ], "extra": [ 1, 78, 119, 145, 5, 141, 18, 77, 201, 6, 161, 189, 217, 239, 176, 66, 81, 203, 73, 84, 103, 7, 37, 252, 205, 156, 100, 171, 110, 28, 122, 243, 78, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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