Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04ec32bc3c0b79ce5ef2040ef0464c73d5df6d4c9470e64db02a8832342feda3

Tx prefix hash: d0fc59e6dfa555102a10eab38c63a4f1e55de5a518e26bf393f494855a553bfa
Tx public key: 87f147629a04456ffc8d72a6b3eaf41f6857a1fda7f8bff18f3a14f2e506f272
Timestamp: 1696399673 Timestamp [UCT]: 2023-10-04 06:07:53 Age [y:d:h:m:s]: 02:036:05:10:22
Block: 862091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545511 RingCT/type: yes/0
Extra: 0187f147629a04456ffc8d72a6b3eaf41f6857a1fda7f8bff18f3a14f2e506f27202110000000afaf35c9c000000000000000000

1 output(s) for total of 0.854151061000 dcy

stealth address amount amount idx
00: 149851e2a3284796f1c44601b7cae36e60fb49a4b2a5ec6cf4e8cb9309f7136a 0.854151061000 1316477 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": 862101, "vin": [ { "gen": { "height": 862091 } } ], "vout": [ { "amount": 854151061, "target": { "key": "149851e2a3284796f1c44601b7cae36e60fb49a4b2a5ec6cf4e8cb9309f7136a" } } ], "extra": [ 1, 135, 241, 71, 98, 154, 4, 69, 111, 252, 141, 114, 166, 179, 234, 244, 31, 104, 87, 161, 253, 167, 248, 191, 241, 143, 58, 20, 242, 229, 6, 242, 114, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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