Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14082535325d4eec6fce53460495760f60223176df16578471234674bb215ed3

Tx prefix hash: 036d8c6cb0f685918f20fb247f4bd4bbf51a773f1868e6c1ddfb66b35710ee2f
Tx public key: dcb57b2ef4a11c6683930ce0fdac10fbaa774cd06302653e32f6acb1bf64b351
Timestamp: 1698339045 Timestamp [UCT]: 2023-10-26 16:50:45 Age [y:d:h:m:s]: 01:154:12:19:17
Block: 878205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371406 RingCT/type: yes/0
Extra: 01dcb57b2ef4a11c6683930ce0fdac10fbaa774cd06302653e32f6acb1bf64b3510211000000034b8f5122000000000000000000

1 output(s) for total of 0.755339663000 dcy

stealth address amount amount idx
00: 446d698598076c58f6ad31be03f5a0a97ea4eeda4cdcd1f7e5f302e872dcdf5b 0.755339663000 1333629 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": 878215, "vin": [ { "gen": { "height": 878205 } } ], "vout": [ { "amount": 755339663, "target": { "key": "446d698598076c58f6ad31be03f5a0a97ea4eeda4cdcd1f7e5f302e872dcdf5b" } } ], "extra": [ 1, 220, 181, 123, 46, 244, 161, 28, 102, 131, 147, 12, 224, 253, 172, 16, 251, 170, 119, 76, 208, 99, 2, 101, 62, 50, 246, 172, 177, 191, 100, 179, 81, 2, 17, 0, 0, 0, 3, 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