Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a19504da9129cca749119bf9694ef79d77710573e74e7dc288ee059bb84d7558

Tx prefix hash: 6255f3b7a9ad693c038acb1d60a06b50afef727a3ea3a4a7317e7eb598472ad4
Tx public key: 2b5485b30c6044cf2e232e482d32be29e9b12a1dbed882bd06f09de7710a2a34
Timestamp: 1696229737 Timestamp [UCT]: 2023-10-02 06:55:37 Age [y:d:h:m:s]: 01:105:15:28:06
Block: 860691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336772 RingCT/type: yes/0
Extra: 012b5485b30c6044cf2e232e482d32be29e9b12a1dbed882bd06f09de7710a2a3402110000000233af99f4000000000000000000

1 output(s) for total of 0.863323312000 dcy

stealth address amount amount idx
00: e16da2ec89f2dc38345b5d6a0731e25e10103b34cbac9e5aa2909af41d25a09c 0.863323312000 1314987 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": 860701, "vin": [ { "gen": { "height": 860691 } } ], "vout": [ { "amount": 863323312, "target": { "key": "e16da2ec89f2dc38345b5d6a0731e25e10103b34cbac9e5aa2909af41d25a09c" } } ], "extra": [ 1, 43, 84, 133, 179, 12, 96, 68, 207, 46, 35, 46, 72, 45, 50, 190, 41, 233, 177, 42, 29, 190, 216, 130, 189, 6, 240, 157, 231, 113, 10, 42, 52, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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