Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebc1f381676f18e9e35cc5e4c25cb62ee4e86585247603734067a8eb0b76a787

Tx prefix hash: 0cae841b731fb8ad04eb4e140c4f5bd5544d9a98b6f1530347ccd3532760db60
Tx public key: 8eebaee94520b4d616097c37834543f08fac376a3458ee2a860b5b69b6d897d2
Timestamp: 1707104535 Timestamp [UCT]: 2024-02-05 03:42:15 Age [y:d:h:m:s]: 01:058:21:04:51
Block: 950634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303144 RingCT/type: yes/0
Extra: 018eebaee94520b4d616097c37834543f08fac376a3458ee2a860b5b69b6d897d202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea2e0aa60be7e55f3d4300009c55b0fe7716e6a823d5557260a06fbf140a4cc 0.600000000000 1409282 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": 950644, "vin": [ { "gen": { "height": 950634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea2e0aa60be7e55f3d4300009c55b0fe7716e6a823d5557260a06fbf140a4cc" } } ], "extra": [ 1, 142, 235, 174, 233, 69, 32, 180, 214, 22, 9, 124, 55, 131, 69, 67, 240, 143, 172, 55, 106, 52, 88, 238, 42, 134, 11, 91, 105, 182, 216, 151, 210, 2, 17, 0, 0, 0, 1, 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