Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 778488b6a6168af58f7b588f46f3ec595fb77412950bdfe7c9979c019b12f2b5

Tx prefix hash: b24ae058bba0b2684caa135a64470f9c9e8fd76bbb323f519e3090c5761323de
Tx public key: 295e8466351a9f5aef51c20dfafc37c1e5cf6b033cc205b6edd84899c4663a24
Timestamp: 1730057451 Timestamp [UCT]: 2024-10-27 19:30:51 Age [y:d:h:m:s]: 00:148:02:09:22
Block: 1140896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105626 RingCT/type: yes/0
Extra: 01295e8466351a9f5aef51c20dfafc37c1e5cf6b033cc205b6edd84899c4663a24021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b37db53fcc95d7c3be53a5920fa7b3cbbe1e0e7ce1e98fb23e15d2b2567a6f76 0.600000000000 1624699 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": 1140906, "vin": [ { "gen": { "height": 1140896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b37db53fcc95d7c3be53a5920fa7b3cbbe1e0e7ce1e98fb23e15d2b2567a6f76" } } ], "extra": [ 1, 41, 94, 132, 102, 53, 26, 159, 90, 239, 81, 194, 13, 250, 252, 55, 193, 229, 207, 107, 3, 60, 194, 5, 182, 237, 216, 72, 153, 196, 102, 58, 36, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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