Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e87e1b2143c07a47be79a3a8de5b6887a7f871901cb05e83c51bee2570899920

Tx prefix hash: b285b8140c9ebe1935a598e5abb632676dcefca2b32cc5e642363e64a6a24cff
Tx public key: e91267b45c0ece9e59f03fbbb0b330b152e2b1510734f49e8a3732a1e00f4cbf
Timestamp: 1732972148 Timestamp [UCT]: 2024-11-30 13:09:08 Age [y:d:h:m:s]: 01:021:11:22:02
Block: 1165004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273793 RingCT/type: yes/0
Extra: 01e91267b45c0ece9e59f03fbbb0b330b152e2b1510734f49e8a3732a1e00f4cbf021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70f153df48ef1e953ce8b9371a52cd4593e713fd502977c462f372a9fe328232 0.600000000000 1650679 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": 1165014, "vin": [ { "gen": { "height": 1165004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70f153df48ef1e953ce8b9371a52cd4593e713fd502977c462f372a9fe328232" } } ], "extra": [ 1, 233, 18, 103, 180, 92, 14, 206, 158, 89, 240, 63, 187, 176, 179, 48, 177, 82, 226, 177, 81, 7, 52, 244, 158, 138, 55, 50, 161, 224, 15, 76, 191, 2, 17, 0, 0, 0, 1, 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