Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdc8b4354a11abfa9054c29e39ea0675fa2e994eb7cea97c4976e9033e10c781

Tx prefix hash: a8b72a6b1b8a2e2da21b690ae02f00539abd0aa47d588c56f188fcfb6bb16d25
Tx public key: cccc2e618a5a6e4509d22ed830f18d0e841dc022f2938a38c5108b34cba7fac3
Timestamp: 1699606517 Timestamp [UCT]: 2023-11-10 08:55:17 Age [y:d:h:m:s]: 01:083:02:03:07
Block: 888490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320536 RingCT/type: yes/0
Extra: 01cccc2e618a5a6e4509d22ed830f18d0e841dc022f2938a38c5108b34cba7fac30211000000014b8f5122000000000000000000

1 output(s) for total of 0.698334986000 dcy

stealth address amount amount idx
00: 086c1b5ca4455f9afe40a263cff7465e9eeeacf1ddb4f3b357dacbed157d2858 0.698334986000 1344433 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": 888500, "vin": [ { "gen": { "height": 888490 } } ], "vout": [ { "amount": 698334986, "target": { "key": "086c1b5ca4455f9afe40a263cff7465e9eeeacf1ddb4f3b357dacbed157d2858" } } ], "extra": [ 1, 204, 204, 46, 97, 138, 90, 110, 69, 9, 210, 46, 216, 48, 241, 141, 14, 132, 29, 192, 34, 242, 147, 138, 56, 197, 16, 139, 52, 203, 167, 250, 195, 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