Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3296706b631c3486085a81592dc7815fc83c1b1dad0f16358754a0716998d6e5

Tx prefix hash: ae878b942f3929dcae69a6afcc5db9e96a42e8bdfee1dc426e6a471a39d423ac
Tx public key: 4bd8a631f73691c658ccc4cda29b3c9f1dab48f03777e0a30d3c39737b53b2d2
Timestamp: 1708802122 Timestamp [UCT]: 2024-02-24 19:15:22 Age [y:d:h:m:s]: 00:260:14:46:02
Block: 964723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186574 RingCT/type: yes/0
Extra: 014bd8a631f73691c658ccc4cda29b3c9f1dab48f03777e0a30d3c39737b53b2d202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f5c13ce92db42b4a5bf3092f5d01ed98d1c88b486bf5549a5253ec8276bcbd 0.600000000000 1424466 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": 964733, "vin": [ { "gen": { "height": 964723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f5c13ce92db42b4a5bf3092f5d01ed98d1c88b486bf5549a5253ec8276bcbd" } } ], "extra": [ 1, 75, 216, 166, 49, 247, 54, 145, 198, 88, 204, 196, 205, 162, 155, 60, 159, 29, 171, 72, 240, 55, 119, 224, 163, 13, 60, 57, 115, 123, 83, 178, 210, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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