Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bce1c7443aa9d1d44588b2f46cff23ac68e72ce59885178281141729ffeaf968

Tx prefix hash: bb66be829999b0e1ff0544f674743115f9df83bbbca9f8ad6b069afa15b713b6
Tx public key: 2793bec9be97047d5a4ff723ff4d68f74c5a044a8dca75e1c9495e8919b2da9f
Timestamp: 1725063992 Timestamp [UCT]: 2024-08-31 00:26:32 Age [y:d:h:m:s]: 00:216:12:07:17
Block: 1099537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154590 RingCT/type: yes/0
Extra: 012793bec9be97047d5a4ff723ff4d68f74c5a044a8dca75e1c9495e8919b2da9f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3fdd391f836819a007b88b93fbe36ad8d9e8dbd4017a68cf4cccfd1def09fed 0.600000000000 1575500 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": 1099547, "vin": [ { "gen": { "height": 1099537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3fdd391f836819a007b88b93fbe36ad8d9e8dbd4017a68cf4cccfd1def09fed" } } ], "extra": [ 1, 39, 147, 190, 201, 190, 151, 4, 125, 90, 79, 247, 35, 255, 77, 104, 247, 76, 90, 4, 74, 141, 202, 117, 225, 201, 73, 94, 137, 25, 178, 218, 159, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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