Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c383249461f28fc8cb3af763a57a16faf5d1f5cb3e4c7ec9e39262fb0ba709

Tx prefix hash: a83add5626cf9a530508c01f73b3d1f11eaaa5ebb9bf1d605e888bb2feaf885c
Tx public key: 53b3a6407567747568a21d385e293e45c17fb960325574d09d5eeb7762886c1a
Timestamp: 1674058982 Timestamp [UCT]: 2023-01-18 16:23:02 Age [y:d:h:m:s]: 02:103:17:42:49
Block: 677542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595816 RingCT/type: yes/0
Extra: 0153b3a6407567747568a21d385e293e45c17fb960325574d09d5eeb7762886c1a0211000000058b7b6602000000000000000000

1 output(s) for total of 3.491580337000 dcy

stealth address amount amount idx
00: e656aca3de06fb15781c6e65dd09dac78497f2d6f2c8ec2d702ed1adb29738e2 3.491580337000 1119325 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": 677552, "vin": [ { "gen": { "height": 677542 } } ], "vout": [ { "amount": 3491580337, "target": { "key": "e656aca3de06fb15781c6e65dd09dac78497f2d6f2c8ec2d702ed1adb29738e2" } } ], "extra": [ 1, 83, 179, 166, 64, 117, 103, 116, 117, 104, 162, 29, 56, 94, 41, 62, 69, 193, 127, 185, 96, 50, 85, 116, 208, 157, 94, 235, 119, 98, 136, 108, 26, 2, 17, 0, 0, 0, 5, 139, 123, 102, 2, 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