Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cf2d12e36e16507db33382a0935b046c998a79cd9d07f6072dc139051f6e6ec

Tx prefix hash: 1a6e3ea773717f57295c6165f82be76b1f8f1cb70d9d680859a5c63b3317d30a
Tx public key: 71c0e5db537d1573a28dffe3d0f83b2b8745aa3060c2a1255711c24dca0c8ba8
Timestamp: 1698454288 Timestamp [UCT]: 2023-10-28 00:51:28 Age [y:d:h:m:s]: 02:073:17:41:07
Block: 879145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 572365 RingCT/type: yes/0
Extra: 0171c0e5db537d1573a28dffe3d0f83b2b8745aa3060c2a1255711c24dca0c8ba80211000000024b8f5122000000000000000000

1 output(s) for total of 0.749942003000 dcy

stealth address amount amount idx
00: 4b60589d0e33d3c01db7bd896c6c201fb6dd967cec76cb581b0ad7e185b42c04 0.749942003000 1334647 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": 879155, "vin": [ { "gen": { "height": 879145 } } ], "vout": [ { "amount": 749942003, "target": { "key": "4b60589d0e33d3c01db7bd896c6c201fb6dd967cec76cb581b0ad7e185b42c04" } } ], "extra": [ 1, 113, 192, 229, 219, 83, 125, 21, 115, 162, 141, 255, 227, 208, 248, 59, 43, 135, 69, 170, 48, 96, 194, 161, 37, 87, 17, 194, 77, 202, 12, 139, 168, 2, 17, 0, 0, 0, 2, 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